You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Dan Rollo <da...@gmail.com> on 2017/01/06 03:24:22 UTC
svn error with http checkout (was: Re: about 3.0 artifacts and
announcement)
I was just trying to do a clean checkout from “trunk” to test the build/release steps (and hopefully help with publishing binaries to Central), but I’m getting a subversion error during checkout:
$ svn checkout http://svn.apache.org/repos/asf/river/jtsk/trunk river
A river/test
A river/test/conf
...
A river/test/src/org/apache/river/concurrent/ReferenceMapTest.java
A river/test/quarantined-src/README
svn: E175002: GET request returned unexpected delta base: /repos/asf/!svn/rvr/1726456/river/jtsk/trunk/LICENSE
Anybody else seeing similar issues with a clean checkout using “http” (anonymous) url?
For kicks, I also tried the https URL given under the ‘Developer Access’ section (show below), and that worked.
Is this expected? If so, maybe we should change the 'Anonymous access’ URL docs to use https.
$ svn checkout https://svn.apache.org/repos/asf/river/jtsk/trunk river
-Dan
From: Zsolt Kúti <la.tinca@gmail.com <ma...@gmail.com>>
Subject: about 3.0 artifacts and announcement
Date: January 5, 2017 at 3:51:07 PM EST
To: dev@river.apache.org <ma...@river.apache.org>
Hi,
Can somebody tell if our release process documentation is up-to date:
http://river.apache.org/dev-doc/building-a-release.html <http://river.apache.org/dev-doc/building-a-release.html>
As to the release, the last mail was:
http://mail-archives.apache.org/mod_mbox/river-dev/201610.mbox/%3cCAK_o9cH7JPsfd_CK4-pOGb3nswH4R8jB1Kh6=UTWF2c0Ge9V=w@mail.gmail.com%3e <http://mail-archives.apache.org/mod_mbox/river-dev/201610.mbox/%3cCAK_o9cH7JPsfd_CK4-pOGb3nswH4R8jB1Kh6=UTWF2c0Ge9V=w@mail.gmail.com%3e>
The 3.0.0 release artifacts (no binary) are available from here:
http://www.apache.org/dyn/closer.cgi/river/ <http://www.apache.org/dyn/closer.cgi/river/>
So nothing is against a release announcement on our website, isn't it?
If nobody else is willing to, I can take a look into how to add our jars to
maven repo,.
Cheers,
Zsolt
Re: svn error with http checkout (was: Re: about 3.0 artifacts and announcement)
Posted by Niclas Hedhman <ni...@hedhman.org>.
Works for me with SVN 1.9.5 on Linux Debian.
In principle, ASF wants all URLs to be https, but it should not impact this
case. In any event, I don't think there is anything for the River project
to do about it right now.
Cheers
Niclas
On Fri, Jan 6, 2017 at 11:52 AM, Dan Rollo <da...@gmail.com> wrote:
> Sorry, forgot to include my subversion version info:
>
> $ svn --version
> svn, version 1.9.4 (r1740329)
> compiled Nov 15 2016, 20:35:27 on x86_64-apple-darwin15.0.0
>
> > On Jan 5, 2017, at 10:24 PM, Dan Rollo <da...@gmail.com> wrote:
> >
> > I was just trying to do a clean checkout from “trunk” to test the
> build/release steps (and hopefully help with publishing binaries to
> Central), but I’m getting a subversion error during checkout:
> >
> >
> > $ svn checkout http://svn.apache.org/repos/asf/river/jtsk/trunk <
> http://svn.apache.org/repos/asf/river/jtsk/trunk> river
> > A river/test
> > A river/test/conf
> > ...
> > A river/test/src/org/apache/river/concurrent/ReferenceMapTest.java
> > A river/test/quarantined-src/README
> > svn: E175002: GET request returned unexpected delta base:
> /repos/asf/!svn/rvr/1726456/river/jtsk/trunk/LICENSE
> >
> > Anybody else seeing similar issues with a clean checkout using “http”
> (anonymous) url?
> >
> >
> > For kicks, I also tried the https URL given under the ‘Developer Access’
> section (show below), and that worked.
> > Is this expected? If so, maybe we should change the 'Anonymous access’
> URL docs to use https.
> >
> > $ svn checkout https://svn.apache.org/repos/asf/river/jtsk/trunk <
> https://svn.apache.org/repos/asf/river/jtsk/trunk> river
> >
> >
> > -Dan
> >
> >
> >
> > From: Zsolt Kúti <la.tinca@gmail.com <ma...@gmail.com>>
> > Subject: about 3.0 artifacts and announcement
> > Date: January 5, 2017 at 3:51:07 PM EST
> > To: dev@river.apache.org <ma...@river.apache.org>
> >
> >
> > Hi,
> >
> > Can somebody tell if our release process documentation is up-to date:
> > http://river.apache.org/dev-doc/building-a-release.html <
> http://river.apache.org/dev-doc/building-a-release.html>
> >
> > As to the release, the last mail was:
> > http://mail-archives.apache.org/mod_mbox/river-dev/201610.
> mbox/%3cCAK_o9cH7JPsfd_CK4-pOGb3nswH4R8jB1Kh6=
> UTWF2c0Ge9V=w@mail.gmail.com%3e <http://mail-archives.apache.
> org/mod_mbox/river-dev/201610.mbox/%3cCAK_o9cH7JPsfd_CK4-
> pOGb3nswH4R8jB1Kh6=UTWF2c0Ge9V=w@mail.gmail.com%3e>
> >
> > The 3.0.0 release artifacts (no binary) are available from here:
> > http://www.apache.org/dyn/closer.cgi/river/ <http://www.apache.org/dyn/
> closer.cgi/river/>
> > So nothing is against a release announcement on our website, isn't it?
> >
> >
> > If nobody else is willing to, I can take a look into how to add our jars
> to
> > maven repo,.
> >
> > Cheers,
> > Zsolt
>
>
--
Niclas Hedhman, Software Developer
http://polygene.apache.org <http://zest.apache.org> - New Energy for Java
Re: svn error with http checkout (was: Re: about 3.0 artifacts and
announcement)
Posted by Dan Rollo <da...@gmail.com>.
Sorry, forgot to include my subversion version info:
$ svn --version
svn, version 1.9.4 (r1740329)
compiled Nov 15 2016, 20:35:27 on x86_64-apple-darwin15.0.0
> On Jan 5, 2017, at 10:24 PM, Dan Rollo <da...@gmail.com> wrote:
>
> I was just trying to do a clean checkout from “trunk” to test the build/release steps (and hopefully help with publishing binaries to Central), but I’m getting a subversion error during checkout:
>
>
> $ svn checkout http://svn.apache.org/repos/asf/river/jtsk/trunk <http://svn.apache.org/repos/asf/river/jtsk/trunk> river
> A river/test
> A river/test/conf
> ...
> A river/test/src/org/apache/river/concurrent/ReferenceMapTest.java
> A river/test/quarantined-src/README
> svn: E175002: GET request returned unexpected delta base: /repos/asf/!svn/rvr/1726456/river/jtsk/trunk/LICENSE
>
> Anybody else seeing similar issues with a clean checkout using “http” (anonymous) url?
>
>
> For kicks, I also tried the https URL given under the ‘Developer Access’ section (show below), and that worked.
> Is this expected? If so, maybe we should change the 'Anonymous access’ URL docs to use https.
>
> $ svn checkout https://svn.apache.org/repos/asf/river/jtsk/trunk <https://svn.apache.org/repos/asf/river/jtsk/trunk> river
>
>
> -Dan
>
>
>
> From: Zsolt Kúti <la.tinca@gmail.com <ma...@gmail.com>>
> Subject: about 3.0 artifacts and announcement
> Date: January 5, 2017 at 3:51:07 PM EST
> To: dev@river.apache.org <ma...@river.apache.org>
>
>
> Hi,
>
> Can somebody tell if our release process documentation is up-to date:
> http://river.apache.org/dev-doc/building-a-release.html <http://river.apache.org/dev-doc/building-a-release.html>
>
> As to the release, the last mail was:
> http://mail-archives.apache.org/mod_mbox/river-dev/201610.mbox/%3cCAK_o9cH7JPsfd_CK4-pOGb3nswH4R8jB1Kh6=UTWF2c0Ge9V=w@mail.gmail.com%3e <http://mail-archives.apache.org/mod_mbox/river-dev/201610.mbox/%3cCAK_o9cH7JPsfd_CK4-pOGb3nswH4R8jB1Kh6=UTWF2c0Ge9V=w@mail.gmail.com%3e>
>
> The 3.0.0 release artifacts (no binary) are available from here:
> http://www.apache.org/dyn/closer.cgi/river/ <http://www.apache.org/dyn/closer.cgi/river/>
> So nothing is against a release announcement on our website, isn't it?
>
>
> If nobody else is willing to, I can take a look into how to add our jars to
> maven repo,.
>
> Cheers,
> Zsolt
Re: svn error with http checkout (was: Re: about 3.0 artifacts and announcement)
Posted by Zsolt Kúti <la...@gmail.com>.
Yes, sure. Just wanted to be 100% sure that it was not interfering in any
ways with my other checkout (the https one).
On Fri, Jan 6, 2017 at 4:32 PM, Niclas Hedhman <ni...@hedhman.org> wrote:
> I don't think commit should work on http, it should only be allowed on
> https.
>
> On Fri, Jan 6, 2017 at 2:36 PM, Zsolt Kúti <la...@gmail.com> wrote:
>
> > Just made a fresh http checkout (done with IDEA). It went fine, on commit
> > it asked for special credentials.
> >
> > Zsolt
> >
> > On Fri, Jan 6, 2017 at 4:24 AM, Dan Rollo <da...@gmail.com> wrote:
> >
> > > I was just trying to do a clean checkout from “trunk” to test the
> > > build/release steps (and hopefully help with publishing binaries to
> > > Central), but I’m getting a subversion error during checkout:
> > >
> > >
> > > $ svn checkout http://svn.apache.org/repos/asf/river/jtsk/trunk river
> > > A river/test
> > > A river/test/conf
> > > ...
> > > A river/test/src/org/apache/river/concurrent/ReferenceMapTest.java
> > > A river/test/quarantined-src/README
> > > svn: E175002: GET request returned unexpected delta base:
> > > /repos/asf/!svn/rvr/1726456/river/jtsk/trunk/LICENSE
> > >
> > > Anybody else seeing similar issues with a clean checkout using “http”
> > > (anonymous) url?
> > >
> > >
> > > For kicks, I also tried the https URL given under the ‘Developer
> Access’
> > > section (show below), and that worked.
> > > Is this expected? If so, maybe we should change the 'Anonymous access’
> > URL
> > > docs to use https.
> > >
> > > $ svn checkout https://svn.apache.org/repos/asf/river/jtsk/trunk river
> > >
> > >
> > > -Dan
> > >
> > >
> > >
> > > From: Zsolt Kúti <la.tinca@gmail.com <ma...@gmail.com>>
> > > Subject: about 3.0 artifacts and announcement
> > > Date: January 5, 2017 at 3:51:07 PM EST
> > > To: dev@river.apache.org <ma...@river.apache.org>
> > >
> > >
> > > Hi,
> > >
> > > Can somebody tell if our release process documentation is up-to date:
> > > http://river.apache.org/dev-doc/building-a-release.html <
> > > http://river.apache.org/dev-doc/building-a-release.html>
> > >
> > > As to the release, the last mail was:
> > > http://mail-archives.apache.org/mod_mbox/river-dev/201610.
> > > mbox/%3cCAK_o9cH7JPsfd_CK4-pOGb3nswH4R8jB1Kh6=
> > > UTWF2c0Ge9V=w@mail.gmail.com%3e <http://mail-archives.apache.
> > > org/mod_mbox/river-dev/201610.mbox/%3cCAK_o9cH7JPsfd_CK4-
> > > pOGb3nswH4R8jB1Kh6=UTWF2c0Ge9V=w@mail.gmail.com%3e>
> > >
> > > The 3.0.0 release artifacts (no binary) are available from here:
> > > http://www.apache.org/dyn/closer.cgi/river/ <
> http://www.apache.org/dyn/
> > > closer.cgi/river/>
> > > So nothing is against a release announcement on our website, isn't it?
> > >
> > >
> > > If nobody else is willing to, I can take a look into how to add our
> jars
> > to
> > > maven repo,.
> > >
> > > Cheers,
> > > Zsolt
> >
>
>
>
> --
> Niclas Hedhman, Software Developer
> http://polygene.apache.org <http://zest.apache.org> - New Energy for Java
>
Re: svn error with http checkout (was: Re: about 3.0 artifacts and announcement)
Posted by Niclas Hedhman <ni...@hedhman.org>.
I don't think commit should work on http, it should only be allowed on
https.
On Fri, Jan 6, 2017 at 2:36 PM, Zsolt Kúti <la...@gmail.com> wrote:
> Just made a fresh http checkout (done with IDEA). It went fine, on commit
> it asked for special credentials.
>
> Zsolt
>
> On Fri, Jan 6, 2017 at 4:24 AM, Dan Rollo <da...@gmail.com> wrote:
>
> > I was just trying to do a clean checkout from “trunk” to test the
> > build/release steps (and hopefully help with publishing binaries to
> > Central), but I’m getting a subversion error during checkout:
> >
> >
> > $ svn checkout http://svn.apache.org/repos/asf/river/jtsk/trunk river
> > A river/test
> > A river/test/conf
> > ...
> > A river/test/src/org/apache/river/concurrent/ReferenceMapTest.java
> > A river/test/quarantined-src/README
> > svn: E175002: GET request returned unexpected delta base:
> > /repos/asf/!svn/rvr/1726456/river/jtsk/trunk/LICENSE
> >
> > Anybody else seeing similar issues with a clean checkout using “http”
> > (anonymous) url?
> >
> >
> > For kicks, I also tried the https URL given under the ‘Developer Access’
> > section (show below), and that worked.
> > Is this expected? If so, maybe we should change the 'Anonymous access’
> URL
> > docs to use https.
> >
> > $ svn checkout https://svn.apache.org/repos/asf/river/jtsk/trunk river
> >
> >
> > -Dan
> >
> >
> >
> > From: Zsolt Kúti <la.tinca@gmail.com <ma...@gmail.com>>
> > Subject: about 3.0 artifacts and announcement
> > Date: January 5, 2017 at 3:51:07 PM EST
> > To: dev@river.apache.org <ma...@river.apache.org>
> >
> >
> > Hi,
> >
> > Can somebody tell if our release process documentation is up-to date:
> > http://river.apache.org/dev-doc/building-a-release.html <
> > http://river.apache.org/dev-doc/building-a-release.html>
> >
> > As to the release, the last mail was:
> > http://mail-archives.apache.org/mod_mbox/river-dev/201610.
> > mbox/%3cCAK_o9cH7JPsfd_CK4-pOGb3nswH4R8jB1Kh6=
> > UTWF2c0Ge9V=w@mail.gmail.com%3e <http://mail-archives.apache.
> > org/mod_mbox/river-dev/201610.mbox/%3cCAK_o9cH7JPsfd_CK4-
> > pOGb3nswH4R8jB1Kh6=UTWF2c0Ge9V=w@mail.gmail.com%3e>
> >
> > The 3.0.0 release artifacts (no binary) are available from here:
> > http://www.apache.org/dyn/closer.cgi/river/ <http://www.apache.org/dyn/
> > closer.cgi/river/>
> > So nothing is against a release announcement on our website, isn't it?
> >
> >
> > If nobody else is willing to, I can take a look into how to add our jars
> to
> > maven repo,.
> >
> > Cheers,
> > Zsolt
>
--
Niclas Hedhman, Software Developer
http://polygene.apache.org <http://zest.apache.org> - New Energy for Java
Re: svn error with http checkout (was: Re: about 3.0 artifacts and announcement)
Posted by Zsolt Kúti <la...@gmail.com>.
Just made a fresh http checkout (done with IDEA). It went fine, on commit
it asked for special credentials.
Zsolt
On Fri, Jan 6, 2017 at 4:24 AM, Dan Rollo <da...@gmail.com> wrote:
> I was just trying to do a clean checkout from “trunk” to test the
> build/release steps (and hopefully help with publishing binaries to
> Central), but I’m getting a subversion error during checkout:
>
>
> $ svn checkout http://svn.apache.org/repos/asf/river/jtsk/trunk river
> A river/test
> A river/test/conf
> ...
> A river/test/src/org/apache/river/concurrent/ReferenceMapTest.java
> A river/test/quarantined-src/README
> svn: E175002: GET request returned unexpected delta base:
> /repos/asf/!svn/rvr/1726456/river/jtsk/trunk/LICENSE
>
> Anybody else seeing similar issues with a clean checkout using “http”
> (anonymous) url?
>
>
> For kicks, I also tried the https URL given under the ‘Developer Access’
> section (show below), and that worked.
> Is this expected? If so, maybe we should change the 'Anonymous access’ URL
> docs to use https.
>
> $ svn checkout https://svn.apache.org/repos/asf/river/jtsk/trunk river
>
>
> -Dan
>
>
>
> From: Zsolt Kúti <la.tinca@gmail.com <ma...@gmail.com>>
> Subject: about 3.0 artifacts and announcement
> Date: January 5, 2017 at 3:51:07 PM EST
> To: dev@river.apache.org <ma...@river.apache.org>
>
>
> Hi,
>
> Can somebody tell if our release process documentation is up-to date:
> http://river.apache.org/dev-doc/building-a-release.html <
> http://river.apache.org/dev-doc/building-a-release.html>
>
> As to the release, the last mail was:
> http://mail-archives.apache.org/mod_mbox/river-dev/201610.
> mbox/%3cCAK_o9cH7JPsfd_CK4-pOGb3nswH4R8jB1Kh6=
> UTWF2c0Ge9V=w@mail.gmail.com%3e <http://mail-archives.apache.
> org/mod_mbox/river-dev/201610.mbox/%3cCAK_o9cH7JPsfd_CK4-
> pOGb3nswH4R8jB1Kh6=UTWF2c0Ge9V=w@mail.gmail.com%3e>
>
> The 3.0.0 release artifacts (no binary) are available from here:
> http://www.apache.org/dyn/closer.cgi/river/ <http://www.apache.org/dyn/
> closer.cgi/river/>
> So nothing is against a release announcement on our website, isn't it?
>
>
> If nobody else is willing to, I can take a look into how to add our jars to
> maven repo,.
>
> Cheers,
> Zsolt