Oolite Bulletins

Not quite fixed yet, I'm sorry to report.

I didn't noticed when I posted that error message, but re-reading it, it turned out that it borked again because ~/GNUstep/Applications/Oolite-trunk/oolite.app/oolite-update had somehow reverted back to terrastorage.[color=#FF0000]dyndns[/color].info once more.

After your 'fixed' message, I had to manually edit the above file back to terrastorage.[color=#FF0000]no-ip[/color].info before I could update to 1.79.0.5741-140514-5935cd5.

However, now that has successfully updated, I see that ~/GNUstep/Applications/Oolite-trunk/oolite.app/oolite-update has once again reverted back to terrastorage.[color=#FF0000]dyndns[/color].info.

Something keeps causing that script to return to the old version. Is it the copy that's stored with the source-code that's the problem, perhaps?

Then something has gone wrong with the source code update that I performed on git some couple of weeks ago.
I just looked into the server part...

OK. That's very good that you pinpointed the issue.

I will look into it tonight. Thank you man!

The latest nightly, 14eae08, is still pushing the reversion to dyndns..

Can you, please, try with today's nightly?
I have checked the rsync repository and it seems that it is OK now.

Sorry but I only managed to troubleshoot it last afternoon.

All fixed now.. many thanks..

Good. Apologies for the delay.

I'm getting the following when trying to update trunk

Smivs wrote:

Trying rsync://terrastorage.dyndns.info/oolite-trunk-linux-64...

Replace dyndns to no-ip in oolite.app/oolite-update.

That worked Many thanks Norby

Discussion on failing pulseaudio moved at
Failed to initialize backend "pulse"

This is just a heads up for an upcoming nightly server outage due to nightly server ISP change.

The expected change is to happen in a couple of weeks and, in the worst case, we will loose not more than two nightly builds.
The change will not impact the server name, however, I will still have to setup the new ISP network device.

If the ISP change takes longer, we will risk to have a much bigger outage (a couple of weeks ) since I will be away.
To help with bug fixing delivery planning, I will keep posting weekly updates here.


EDIT:
Following to a new offer from my current ISP, the change is postponed for a year; planned downtime cancelled.

Following a server update that didn't go THAT smoothly, the latest trunk nightly is available.

Getafix wrote:

Following a server update that didn't go THAT smoothly, the latest trunk nightly is available.

I'm sorry to report that it went even less smoothly than you thought..

All working again now, I see..

terrastorage.no-ip.info seems to be offline.. all connection attempts time out.