I think the issue with dist/release/commons is that you need to be listed as a project committer, i.e. you need to be a Commons committer.
Possibly the same applies to Nexus. I have added you as a Commons committer. On Tue, 18 Dec 2018 at 16:24, Maxim Solodovnik <solomax...@gmail.com> wrote: > > Thanks a lot for the help :) > Glad to check the release process ;) > > On Tue, 18 Dec 2018 at 23:19, Gilles <gil...@harfang.homelinux.org> wrote: > > > Hello. > > > > On Tue, 18 Dec 2018 23:05:12 +0700, Maxim Solodovnik wrote: > > > 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 :) > > > > I don't know how to change the permissions (I don't think I have > > the privilege anyway), and the PMC chair is AFK for a couple more > > days IIUC. :-( > > > > Perhaps someone with a taller hat. :-} > > > > Sorry for the inconvenience; it looks like you are first one to > > try and exercise those privileges voted several years ago... > > > > Gilles > > > > > > > > On Tue, 18 Dec 2018 at 22:54, Gilles <gil...@harfang.homelinux.org> > > > 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 > > >> <solomax...@gmail.com> > > >> > 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 > > >> <gil...@harfang.homelinux.org> > > >> >> 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 g...@github.com:apache/commons-collections.git (fetch) > > >> >>> > origin g...@github.com: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? > > >> >>> > > > >> >>> > [...] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > -- > WBR > Maxim aka solomax --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
