SVN resourcespace update 7799 requires new repository path

[Phil Legault]

I try following the instructions

You are using an old repository path. Please use the new repository path:

http://svn.resourcespace.org/svn/rs/trunk

If you are unable to make this change now, to reactivate your system revert to revision 7792:

svn update -r 7792

To make this change:

cd [your resourcespace dir]
svn update -r 7792
svn relocate http://svn.resourcespace.org/svn/rs
svn switch http://svn.resourcespace.org/svn/rs/trunk --ignore-ancestry
svn update

I'm using

svn, version 1.6.11 (r934486)
   compiled Aug  4 2015, 09:07:02

relocate is not available and --ignore-ancestry is not recognized

do you have instructions for svn v 1.6?

I tried svn switch --relocate http://svn.resourcespace.org/svn/rs http://svn.resourcespace.org/svn/rs/trunk --ignore-ancestry

Subcommand 'switch' doesn't accept option '--ignore-ancestry'

I tried svn switch --relocate http://svn.resourcespace.org/svn/rs http://svn.resourcespace.org/svn/rs/trunk

looks like it worked but I get the same instruction screen.

How can I get this to work?

[Dan Huby]

Sorry, I can only suggest upgrading your Subversion client.

I don't have the 1.6 client to do any testing with.

Dan

[Allison M Stec]

For svn 1.6 try "svn switch --relocate" in place of "svn relocate":

"svn switch --relocate http://svn.resourcespace.org/svn/rs"

After that, the other commands should work for you.

--
ResourceSpace: Open Source Digital Asset Management
http://www.resourcespace.org
---
You received this message because you are subscribed to the Google Groups "ResourceSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resourcespac...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
--
ResourceSpace Developer
Reseller of Colorhythm's Prismpoint Portal DAM

[Dan Huby]

I found we were running svn 1.6 on one of our servers - Allison's suggestion was almost right - it just needs two URLs instead. The full sequence is:

svn update -r 7792

svn switch --relocate http://svn.resourcespace.org/svn/resourcespace http://svn.resourcespace.org/svn/rs

svn switch http://svn.resourcespace.org/svn/rs/trunk

Dan

To unsubscribe from this group and stop receiving emails from it, send an email to resourcespace+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Phil Legault]

Thanks Dan

I upgraded the SVN client and was able to get updated

Now I ran an update

#-> svn update

Updating '.':

U    pages/upload_plupload.php

U    pages/upload.php

U    pages/edit_fields/9_ajax/add_keyword.php

U    pages/resource_email.php

U    pages/team/team_dash_admin.php

U    pages/team/team_home.php

U    pages/team/team_dash_tile.php

U    pages/team/team_dash_tile_special.php

U    pages/admin/admin_group_permissions.php

U    pages/admin/admin_resource_type_edit.php

U    pages/search.php

U    pages/user_ratings.php

U    pages/download.php

svn: E175002: GET request failed: 400 Bad Request

I had to roll back to 7799 at least that was a guess and it seemed to work.

I tried to run the update again and I get 

svn: E200014: Checksum mismatch for '/app/resourcespace/pages/upload_plupload.php':

   expected:  50c8fbfae2d2f3920397caec33f50c64

     actual:  34aee413af146e9b11444dc0b337a136

To unsubscribe from this group and stop receiving emails from it, send an email to resourcespac...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Yadin Flammer]

Not seeing this work.  I get to the second switch command:

svn: 'http://svn.montala.net/svn/resourcespace'
is not the same repository as
'http://svn.resourcespace.org/svn/rs'

System is Ubuntu 12 LTS server.  SVN 1.6.17 is the latest version.

[Yadin Flammer]

Seems the actual command needed in step 2 is:
sudo svn switch --relocate http://svn.montala.net/svn/resourcespace http://svn.resourcespace.org/svn/rs

However, step 3 then doesn't just finish the switch, it forced an update to the latest sub revision.
Updated to revision 7995

The desire was to get on the release version as posted at http://www.resourcespace.org/version-history
I issued the normal command to achieve that and it did succeed:
Updated to revision 7966

However, since that is technically NOT an update but a roll back, it is unclear if this will work as desired or if now there is an improper blending of versions.  As a whole, the versioning of this product is unclear and thus far unexplained regarding a production environment as far as test patches vs official releases.

[Dan Huby]

If you want the latest release you should switch to:

http://svn.resourcespace.org/svn/rs/releases/7.7/

Ignore the revision, go for the latest (HEAD).

We will keep this branch up to date with critical bug fixes until the next release is available, which will take the form of a new branch that you will need to switch to.

The paths are confirmed here:

http://www.resourcespace.org/svn

Dan

[Allison Stec]

Dan -

For our non-developer admin types do you think we can create http://svn.resourcespace.org/svn/rs/releases/current/ and always have the current stable version available without switching paths? I'm not sure how much extra work this would be, but I'm guessing it would be much appreciated! Perhaps a generic url could be used that directs to the current release?

Best,
~Allison

--

ResourceSpace: Open Source Digital Asset Management
http://www.resourcespace.org
---
You received this message because you are subscribed to the Google Groups "ResourceSpace" group.

To unsubscribe from this group and stop receiving emails from it, send an email to resourcespac...@googlegroups.com.

[Yadin Flammer]

Clear documentation of these two paths would be greatly appreciated.  Having the instructions in the wiki match the website and this current info would be frankly required.  Right now nothing lines up which causes the problems I've laid out already, and for someone who is not intimately familiar with Subversion it's clear as mud.  For all the things I may know as a sys admin, I'm extremely confused as to what is going on with this product, these releases, these commands, and how to get what I'm looking for at this point.  I don't understand what the difference is between development and release as that's not explained anywhere.  I'm not sure what line I'm on and why and how to maintain.  There are not clear step by step instructions for these two lines and how to use them, it's just vague statements that seem to assume you're already a developer and Subversion expert.  All in all, I have to say it's a pretty poor consumer experience.  I've raised these questions and concerns several times in 3 channels and there doesn't seem to be much care to help clear things up for some reason.  By comparison, any other product I've used on unix you add a repo (if that's even needed) and updates happen when you run updates.  This secondary system with granular versioning in two lines that isn't in any way explained is just a total mystery that really needs to be cleaned up in the documentation.  This issue of the wiki documentation being months or years out of date is a HUGE problem I've brought up before, and again no one seems to be addressing for some reason.  This Google group is also a pretty poor community system.  Montala would do well to bring the documentation from the wiki into a properly maintained documentation site on their servers, as well as implementing proper user support forums.  Sorry for the rant, it's just frustrating to see a product that has so much power and promise and longevity be so poorly organized.  As an admin trying to support users implementing the system it's very troubling to have no sense of stability.

[Dan Huby]

Hi Yadin,

Sorry you're having a bad experience.

The wiki is dated in some areas and we have set up the Knowledge Base as a more polished and user focussed documentation area.

The repository locations to me are very clear on the site, on this page:

http://www.resourcespace.org/svn

The repository switch should not have been too tricky as full instructions were provided to users that upgraded the via the old repository path.

I've sent you repository switching instructions directly but for the benefit of others, here they are:

If your Subversion client is version 1.7 or newer (use 'svn help' to determine):

svn update -r 7792

svn relocate http://svn.resourcespace.org/svn/rs

svn switch http://svn.resourcespace.org/svn/rs/releases/7.7 --ignore-ancestry

If your Subversion client is version 1.6 or older:

svn update -r 7792

svn switch --relocate http://svn.resourcespace.org/svn/resourcespace http://svn.resourcespace.org/svn/rs

svn switch http://svn.resourcespace.org/svn/rs/releases/7.7

I have used this process many times myself and know it to be reliable.

Dan

[Dan Huby]

I thought of that and would love to do that but Subversion doesn't support aliases.

On the other hand though it is nice that you have to make a concious decision to upgrade across versions rather than receive updates for the current release.

Dan

To unsubscribe from this group and stop receiving emails from it, send an email to resourcespace+unsubscribe@googlegroups.com.