git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help with migrating one of OpenJPA classes to commons-collections4


Thanks a lot

Unfortunately the next error is: Failed to deploy artifacts: Could not
transfer artifact org.apache.commons:commons-collections4:jar:4.3 from/to
apache.releases.https (
https://repository.apache.org/service/local/staging/deploy/maven2): Access
denied to:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/commons/commons-collections4/4.3/commons-collections4-4.3.jar

I'm release manger for Apache OpenMeetings and just double-check I can
access Staging Repos at repository.apache.org
, so I guess there are additional restrictions here

would appreciate any help/hint :)

On Tue, 18 Dec 2018 at 22:54, Gilles <gilles@xxxxxxxxxxxxxxxxxxxxx> wrote:

> On Tue, 18 Dec 2018 22:03:04 +0700, Maxim Solodovnik wrote:
> > It seems I'm unable to commit to SVN:
> >
> > URL: https://dist.apache.org/repos/dist/release/commons
> >
> > Sending        KEYS
> > Transmitting file data .svn: E195023: Commit failed (details follow):
> > svn: E195023: Changing file
> > '/home/solomax/work/apache-dist/release/commons/KEYS' is forbidden by
> > the
> > server
> > svn: E175013: Access to
> > '/repos/dist/!svn/txr/31592-qod/release/commons/KEYS' forbidden
> >
> > Can someone help me with access rights?
>
> Not me.
> But I've added your key (revision 31593).
>
> Hope it gets you a little further,
> Gilles
>
> >
> > On Tue, 18 Dec 2018 at 21:22, Maxim Solodovnik <solomax666@xxxxxxxxx>
> > wrote:
> >
> >> Moving conversation to dev@ list
> >>
> >> I was able to create branch using gitbox remote
> >> Will proceed,
> >>
> >> Thanks for the tip
> >>
> >>
> >> On Tue, 18 Dec 2018 at 21:14, Gilles <gilles@xxxxxxxxxxxxxxxxxxxxx>
> >> wrote:
> >>
> >>> Hi.
> >>>
> >>> On Tue, 18 Dec 2018 20:54:22 +0700, Maxim Solodovnik wrote:
> >>> > Hello Gilles,
> >>> >
> >>> > I read documentation and as far as I can see To perform release I
> >>> > need
> >>> > rights to create branch
> >>> >
> >>> > git remote -v
> >>> > origin git@xxxxxxxxxx:apache/commons-collections.git (fetch)
> >>> > origin git@xxxxxxxxxx:apache/commons-collections.git (push)
> >>> >
> >>> > git push -u origin 4.3-release
> >>> > ERROR: Permission to apache/commons-collections.git denied to
> >>> > solomax.
> >>> > fatal: Could not read from remote repository.
> >>> >
> >>> > Please make sure you have the correct access rights
> >>> > and the repository exists.
> >>>
> >>> The repository (at Apache) is here:
> >>>    https://gitbox.apache.org/repos/asf?p=commons-collections.git
> >>>
> >>> We were told that it should now be possible to also write
> >>> through GitHub, but I don't know if and how it should work.
> >>>
> >>> IMO, the easiest would be to clone the above, and try again
> >>> with that.  [If it still does not work, then perhaps the issue
> >>> is that the "all-Apache-committers-are-committers" resolution
> >>> was not applied.]
> >>>
> >>> Gilles
> >>>
> >>> P.S. We should move this conversation over to the "dev" ML.
> >>>
> >>> >
> >>> > Shall I use SVN? Or some other remote?
> >>> >
> >>> >
> >>> >
> >>> > On Tue, 18 Dec 2018 at 16:04, Maxim Solodovnik
> >>> <solomax666@xxxxxxxxx>
> >>> > wrote:
> >>> >
> >>> >> Thanks Gilles,
> >>> >>
> >>> >> will try to create RC tonight
> >>> >>
> >>> >> On Tue, 18 Dec 2018 at 15:55, Gilles
> >>> <gilles@xxxxxxxxxxxxxxxxxxxxx>
> >>> >> wrote:
> >>> >>
> >>> >>> Hi.
> >>> >>>
> >>> >>> On Tue, 18 Dec 2018 09:52:15 +0700, Maxim Solodovnik wrote:
> >>> >>> > I can create RC, no problem
> >>> >>> > But
> >>> >>> > 1) I need my signing key [1] to be added to official KEYS
> >>> >>>
> >>> >>> The file is here:
> >>> >>>    https://dist.apache.org/repos/dist/release/commons/KEYS
> >>> >>>
> >>> >>> > 2) Do you have description of your release process? I was
> >>> unable
> >>> >>> to
> >>> >>> > find one
> >>> >>>
> >>> >>>
> >>> http://commons.apache.org/proper/commons-release-plugin/index.html
> >>> >>>
> >>> >>> Also, a step-by-step recipe is here:
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>>
> >>>
> https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=blob;f=doc/release/release.howto.txt
> >>> >>>
> >>> >>> [It is for a multimodule maven project ("Commons RNG"); it
> >>> >>> mentions problems with the release process that might need
> >>> >>> manual adjustments.]
> >>> >>>
> >>> >>> If you encounter something that does not work as noted,
> >>> >>> please report it here, and on the bug tracking system:
> >>> >>>    https://issues.apache.org/jira/projects/COMMONSSITE
> >>> >>>
> >>> >>> > 3) most probably I will need some rights
> >>> >>>
> >>> >>> The "Commons" project has granted "write" access to all
> >>> >>> Apache committers.
> >>> >>> [But some repositories perhaps miss the actual settings
> >>> >>> to make it work.  You'll have to try...]
> >>> >>>
> >>> >>> HTH,
> >>> >>> Gilles
> >>> >>>
> >>> >>> > [1]
> >>> https://github.com/apache/openmeetings/blob/master/KEYS#L88
> >>> >>> >
> >>> >>> > On Tue, 18 Dec 2018 at 01:06, sebb <sebbaz@xxxxxxxxx> wrote:
> >>> >>> >
> >>> >>> >> On Mon, 17 Dec 2018 at 15:38, Gary Gregory
> >>> >>> <garydgregory@xxxxxxxxx>
> >>> >>> >> wrote:
> >>> >>> >> >
> >>> >>> >> > I am on the road driving this week, my availability is
> >>> >>> limited.
> >>> >>> >> >
> >>> >>> >> > WRT being a RM, I think you need PMC karma for that. Sebb
> >>> >>> might be
> >>> >>> >> able
> >>> >>> >> to
> >>> >>> >> > confirm.
> >>> >>> >>
> >>> >>> >> Creating the dist/dev release candidate only requires
> >>> project
> >>> >>> >> committer karma; Commons requires the same for dist/release
> >>> >>> >>
> >>> >>> >> I don't know about Nexus; I imagine at least LDAP commons
> >>> >>> committer
> >>> >>> >> membership is required.
> >>> >>> >>
> >>> >>> >> There's no harm in trying to create an RC.
> >>> >>> >>
> >>> >>> >> > Gary
> >>> >>> >> >
> >>> >>> >> > On Mon, Dec 17, 2018, 03:59 Gilles
> >>> >>> <gilles@xxxxxxxxxxxxxxxxxxxxx
> >>> >>> >> wrote:
> >>> >>> >> >
> >>> >>> >> > > Hi.
> >>> >>> >> > >
> >>> >>> >> > > On Mon, 17 Dec 2018 15:12:16 +0700, Maxim Solodovnik
> >>> wrote:
> >>> >>> >> > > > Hello Gary,
> >>> >>> >> > > >
> >>> >>> >> > > > Is there any progress? :)
> >>> >>> >> > >
> >>> >>> >> > > Suggestion: Be the release manager of 4.3.
> >>> >>> >> > >
> >>> >>> >> > > Regards,
> >>> >>> >> > > Gilles
> >>> >>> >> > >
> >>> >>> >> > > >
> >>> >>> >> > > > On Tue, 4 Dec 2018 at 00:07, Gary Gregory
> >>> >>> >> <garydgregory@xxxxxxxxx>
> >>> >>> >> > > > wrote:
> >>> >>> >> > > >
> >>> >>> >> > > >> [...]
> >>> >>> >> > >
> >>> >>> >> > >
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>> ---------------------------------------------------------------------
> >>> >>> To unsubscribe, e-mail: user-unsubscribe@xxxxxxxxxxxxxxxxxx
> >>> >>> For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxx
> >>> >>>
> >>> >>>
> >>> >>
> >>> >> --
> >>> >> WBR
> >>> >> Maxim aka solomax
> >>> >>
> >>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: user-unsubscribe@xxxxxxxxxxxxxxxxxx
> >>> For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxx
> >>>
> >>>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx
>
>

-- 
WBR
Maxim aka solomax