error while downloading a svn repo

# 6 years ago
philippeg	Hi tangoers, while trying to get the history of the XPSV2 code with repo http://svn.code.sf.net/p/tango-ds/code/DeviceClasses/Motion/MotorControllers/XPSV2/trunk/src/, I got an error with svn : `svn checkout svn://svn.code.sf.net/p/tango-ds/code/DeviceClasses/Motion/MotorControllers/XPSV2/trunk/ XPSV2-sf A XPSV2-sf/src svn: E185005: Decompression of zlib compressed data failed: size too large` When I tryed to get XPSGroup1.cpp file with firefox, I got a similar error "Decompression of zlib compressed data failed: size too large". It seems linked to the same issue. Do you know how to solve this? My goal is to get not only the current version but also the log history. Thank you. - Philippe

# 6 years ago

Hi tangoers,
while trying to get the history of the XPSV2 code with repo http://svn.code.sf.net/p/tango-ds/code/DeviceClasses/Motion/MotorControllers/XPSV2/trunk/src/, I got an error with svn :


svn checkout svn://svn.code.sf.net/p/tango-ds/code/DeviceClasses/Motion/MotorControllers/XPSV2/trunk/ XPSV2-sf
A    XPSV2-sf/src
svn: E185005: Decompression of zlib compressed data failed: size too large

When I tryed to get XPSGroup1.cpp file with firefox, I got a similar error "Decompression of zlib compressed data failed: size too large". It seems linked to the same issue.

Do you know how to solve this?
My goal is to get not only the current version but also the log history.

Thank you.

- Philippe

# 6 years ago
Reynald	Hi Philippe, It looks like this directory was corrupted at some point as you can see on this commit message in French: https://sourceforge.net/p/tango-ds/code/16443/ It might be difficult to retrieve the history of this XPSGroup.cpp corrupted file but it looks like you can get the history of the other files from the Sourceforge web interface. Cheers, Reynald Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 6 years ago

Reynald

Hi Philippe,

It looks like this directory was corrupted at some point as you can see on this commit message in French:
https://sourceforge.net/p/tango-ds/code/16443/

It might be difficult to retrieve the history of this XPSGroup.cpp corrupted file but it looks like you can get the history of the other files from the Sourceforge web interface.

Cheers,
Reynald

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.

# 6 years ago
philippeg	Thank you, I did not saw this. I understand there is any way yo get the history offline, through svn, am I wrong? The goal would be to check only the differences for this directory. Cheers. Philippe. - Philippe

# 6 years ago
buteau	In fact Philippe This folder XPSV2 of the SVN repo was corrupted years ago without any solution to recover it (despote our efforts and contact with SF online support ) We then decided to transfer the code to another folder called https://sourceforge.net/p/tango-ds/code/HEAD/tree/DeviceClasses/Motion/MotorControllers/XPSV3/ This is the folder containing the version deployed at SOLEIL in operation

# 6 years ago

buteau

In fact Philippe
This folder XPSV2 of the SVN repo was corrupted years ago without any solution to recover it (despote our efforts and contact with SF online support )

We then decided to transfer the code to another folder called https://sourceforge.net/p/tango-ds/code/HEAD/tree/DeviceClasses/Motion/MotorControllers/XPSV3/

This is the folder containing the version deployed at SOLEIL in operation

# 6 years ago
philippeg	Thank you Alain! - Philippe

# 5 years ago
philippeg	Hello, back to this DS, we noticed that Makefile contains @value@ so it seems autoconf is used. Do you know where we can fin informations about build process? Regards - Philippe

# 5 years ago
Reynald	If I were you, I would simply try to regenerate the Makefile with POGO so it would fit your Tango installation. In most of the cases, this is enough. Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago
philippeg	I'm not sure but I though I would need the XMI for this? Is there any other way? It would be simpler indeed. :) - Philippe

# 5 years ago
Reynald	philippeg I'm not sure but I though I would need the XMI for this? This is indeed an old device server with no xmi. POGO used to take a .h file instead of an xmi file. I am not sure the recent versions of POGO are still supporting this feature… You could also create a simple new project with POGO having the same class name and generate only the Makefile… I think the fastest is still to replace these @prefix@ and @ORB_PREFIX@ with the directories where TANGO and OmniORB are installed. Rosenberg's Law: Software is easy to make, except when you want it to do something new. Corollary: The only software that's worth making is software that does something new.

# 5 years ago

Reynald

philippeg
I'm not sure but I though I would need the XMI for this?

This is indeed an old device server with no xmi.
POGO used to take a .h file instead of an xmi file. I am not sure the recent versions of POGO are still supporting this feature…
You could also create a simple new project with POGO having the same class name and generate only the Makefile…

I think the fastest is still to replace these @prefix@ and @ORB_PREFIX@ with the directories where TANGO and OmniORB are installed.

Rosenberg's Law: Software is easy to make, except when you want it to do something new.
Corollary: The only software that's worth making is software that does something new.