Image corrupted after upload to server
-
@danilopinotti So you’re dual booting? It seems that English isn’t your mother tongue, look at this Wikipedia article to see what I mean by “dual booting” https://en.wikipedia.org/wiki/Multi-booting
-
Sorry for my english.
I put an image from another computer (an image with Ubuntu) that this was giving problem. With that, I noticed that the problem is in the Debian image and not on the computer.
Previously, this image Debian did not have this problem. I have no idea why.
Did not do Dual Boot or anything else.I’m better at reading English than to write, so write these means strange phrases.
-
@danilopinotti You’re English is good enough.
You said that previously, the Debian image worked?
What was the last SVN revision that it worked with? And it has previously worked with Debian 7 specifically?
-
@Wayne-Workman Thank you
I don’t remember when I created the image (when it worked) I’ve used the Trunk or still using 1.2.0
-
@danilopinotti Is it possible for you to test using 1.2.0 ?
-
@Wayne-Workman
Today is not possible but tomorrow i can try to arrange this. -
@danilopinotti If you can get it to work in 1.2.0, then it’s just a matter of slowly upgrading that 1.2.0 server through the svn revisions until it no longer works. It would be best if you could build the 1.2.0 server inside of a virtual machine so you can take snapshots before each update and roll back if needed, in order to locate exactly what svn revision fog stops working for this situation.
If we can identify exactly which svn version it stops working with, then it will be easy for the @Developers to fix it.
-
This post is deleted! -
@Wayne-Workman
It would have somewhere that explains how to do to go giving these small changes in SVN?
What is the SVN fog 1.2.0? -
@danilopinotti said:
@Wayne-Workman
It would have somewhere that explains how to do to go giving these small changes in SVN?
What is the SVN fog 1.2.0?1.2.0 is SVN 2094 I believe.
To pull a specific version down, you would use:
svn co -r 2094 https://svn.code.sf.net/p/freeghost/code/trunkAfter getting the initial copy, to update to any specific version, it would be like this:
svn -r 2500 upsvn -r 3000 upsvn -r 3500 upand so on.
Using virtualization and snapshots, you could quickly “go back” when you hit a version that didn’t work, and then start trying versions between the last one and the failed one, to quickly find which version made the change that breaks fog.
Keep in mind that fog DOES NOT support downgrading! Please build a test server to do this testing with!
-
@Wayne-Workman
I do not get my boss’s authority to create virtual machines and test SVNs -
@danilopinotti Then use a real machine to test.
FOG is a community driven project. meaning not just driven by random people, but organizations that use fog as well (mostly organization driven, actually). In order to narrow down what’s wrong, we need to know where it’s wrong.
-
@Wayne-Workman
Do you have any tips to facilitate the process?
Until then I installed FOG and a DHCP server on itself. I would like to update gradually and go testing each SVN? -
@danilopinotti If you can get in touch with me via Chat, I’d be happy to explain and even help out if we could schedule it.
Beyond that, follow the instructions below. Just test it for each revision. When you find one that fails, try the one between the failed version and the last working version you tried. Keep doing that until you find which version it is.
