Author Topic: SVN Certificate Issue (Read 13883 times)

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

leeor_net · « **Reply #1 on:** September 19, 2018, 12:05:12 AM »

Lev does. Should poke him on IRC or shoot him an e-mail.

Vagabond · « **Reply #2 on:** November 19, 2018, 07:44:03 PM »

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

leeor_net · « **Reply #3 on:** November 19, 2018, 09:48:15 PM »

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?)

Hooman · « **Reply #4 on:** November 20, 2018, 08:43:59 PM »

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.

Vagabond · « **Reply #5 on:** November 27, 2018, 09:12:33 PM »

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

Vagabond · « **Reply #6 on:** December 02, 2018, 06:09:55 AM »

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

Hooman · « **Reply #7 on:** December 02, 2018, 02:24:07 PM »

"Yeah!" and there was much rejoicing. Though we were forced to eat Sir Leviathan's minstrels.

Hooman · « **Reply #8 on:** December 03, 2018, 06:31:23 AM »

Is it just me, or is it down again?

Vagabond · « **Reply #9 on:** December 03, 2018, 05:33:44 PM »

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

Hooman · « **Reply #10 on:** December 04, 2018, 12:56:16 AM »

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.

Vagabond · « **Reply #11 on:** December 04, 2018, 06:39:59 PM »

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

Hooman · « **Reply #12 on:** December 06, 2018, 09:52:36 AM »

I think I'd prefer just waiting to get SVN access restored. It gets hard to track things when deviating from standard procedure.

Hooman · « **Reply #13 on:** December 09, 2018, 11:17:52 AM »

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.

Vagabond · « **Reply #14 on:** December 10, 2018, 08:30:57 PM »

Just committed changes to the SVN server and it worked. Good news!

Vagabond · « **Reply #15 on:** January 22, 2019, 07:13:41 PM »

The subversion repository has gone down again.

-Brett

leeor_net · « **Reply #16 on:** January 23, 2019, 10:44:23 PM »

Bah! I'll poke lev again... for real real, though, we should really consider moving entirely away from SVN.

Hooman · « **Reply #17 on:** January 25, 2019, 09:51:14 AM »

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.

Leviathan · « **Reply #18 on:** January 25, 2019, 01:21:07 PM »

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.

leeor_net · « **Reply #19 on:** January 25, 2019, 04:29:40 PM »

This is why I poke you on occasion.

Vagabond · « **Reply #20 on:** January 26, 2019, 08:36:34 AM »

Thanks Leviathan!

Now we need to get that next release of Outpost 2 out.

-Brett

Hooman · « **Reply #21 on:** January 26, 2019, 09:23:36 AM »

Leviathan, what do you mean PM you on telegram? I tried to PM you on IRC and got no response.

leeor_net · « **Reply #22 on:** January 27, 2019, 06:28:50 PM »

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.

Vagabond · « **Reply #23 on:** April 05, 2019, 06:19:43 PM »

Looks like the svn repository is down again. I was going to push updates to some of the code in it.

-Brett

leeor_net · « **Reply #24 on:** April 06, 2019, 01:37:58 PM »

* leeor_net slams head on desk.

I'll bother Lev about it again.

News:

Author Topic: SVN Certificate Issue (Read 13883 times)