Outpost Universe Forums
Community => Feedback/Suggestions/Problems => Topic started by: Vagabond on September 18, 2018, 09:39:06 PM
-
It looks like the SVN certificate needs updating. See attached screenshot. Not sure who has access to fix.
Thanks,
Brett
-
Lev does. Should poke him on IRC or shoot him an e-mail.
-
Wanted to bump this thread. The certificate is still not working right on the SVN. I was sharing Outpost 2 development with someone else and they had to download the repo by accepting the warning which didn't look great on our part.
-Brett
-
Considering we don't actually host the SVN that makes it kind of difficult. Lev seems to have almost entirely lost interest so really I would push to moving everything over to GitHub (that's not infringing, of course) and considering a different solution for the stuff that shouldn't be on a public GitHub project (perhaps GitLab can fill in for this?)
-
I've noticed this recently too.
Would be nice to get things moved over to Git. Though that will take a fair bit of effort to do well, verifying history is both clean and intact. And yeah, GitHub isn't a solution for all projects. We probably do need to fix the SVN certificate issue meanwhile.
-
I've tried the SVN server on two different occasions recently and it now appears to be out of commission. Anyone else have better luck?
Trying to update the changelog in the Outpost 2 game download trunk and push changes to a new scenario for safekeeping.
Thanks,
Brett
-
The SVN server is restored with a valid certificate. Thanks Leviathan! Ok, no excuse for me anymore to not work on getting a new release of Outpost 2 ready. :)
-Brett
-
"Yeah!" and there was much rejoicing. Though we were forced to eat Sir Leviathan's minstrels. :P
-
Is it just me, or is it down again?
-
The Virtual Server now comes up for me but gives an error after a few minutes. So some part of the server still seems to be working, but the data isn't accessible. Did you manage to clone it before it went down again? I did not.
-Brett
-
My git-svn copy is up to date. Actually, it was up to date all along, I just didn't realize it because I checked history of the local master branch, rather than the remote git-svn tracking branch.
My native SVN clone is still out of date. I couldn't remember the update command at the time the server was first back up. Mind you, I could "git svn dcommit" the git-svn clone to a deployed copy of the SVN clone. That would bring it up to date in native SVN format. It might change a bit of meta data though, but all the file changes will be preserved.
In short, our backups aren't in too bad of a shape right now.
-
Could someone repoke Leviathan and see if we can get it back up. I sent him a message today but not sure if he sees them or not.
In the meantime, Hooman do you just want me to email you the updated files for the next release of Outpost 2? I can send one email for each commit. Probably 3 emails in total.
I don't have an opinion on restoring the SVN server with Git-SVN. If you think the lost meta-data is not significant, than I would say just go for it.
Thanks,
Brett
-
I think I'd prefer just waiting to get SVN access restored. It gets hard to track things when deviating from standard procedure.
-
The SVN server is running again.
I've updated my backup copy. I'll look into a way to automating the backup so it stays up to date.
-
Just committed changes to the SVN server and it worked. Good news!
-
The subversion repository has gone down again.
-Brett
-
Bah! I'll poke lev again... for real real, though, we should really consider moving entirely away from SVN.
-
It has been down a lot lately, and kind of hard to get a hold of Lev when it goes down.
Would like to get ForcedExports/OP2Internal ported over to GitHub to work on NetFix updates. Was also thinking the text files that document the internal structures of Outpost 2 can probably be ported over to GitHub.
I'm less certain if the OllyDbg comment files are suitable for GitHub.
-
Hi, Its very easy to get in touch with me. Just pm me on Telegram @leviathan400, I have it installed on all my devices. Have restarted the SVN service. Apologies for any down time.
-
This is why I poke you on occasion. :D
-
Thanks Leviathan!
Now we need to get that next release of Outpost 2 out.
-Brett
-
Leviathan, what do you mean PM you on telegram? I tried to PM you on IRC and got no response.
-
Telegram is a stand-alone app that works as a desktop app, web app and smartphone app. We have a relay bot that posts messages back and forth between a Telegram chat room and IRC. Kind of a kludge but it works.
Anyway, when he says PM him on Telegram, he means via the app versus pinging him through IRC.
-
Looks like the svn repository is down again. I was going to push updates to some of the code in it.
-Brett
-
/me slams head on desk.
I'll bother Lev about it again.
-
Leviathan fixed the SVN server again. Probably best to target a release in the near future.
-Brett
-
That might be an idea. Do you have particular plans for the next release?
There may also be a few projects I might want to port over to GitHub.
-
Well,
we never actually pushed ver 1.3.8 to the website https://forum.outpost2.net/index.php/topic,6107.25.html.
At this point, we should probably wait, clean up current development efforts and then actually push.
-Brett