[ANN] Litecoin v0.6.3 released!

[coblee]

This brings Litecoin up-to-date with the latest Bitcoin fixes. Please update as soon as you can so that you are no longer vulnerable to new DoS attacks that were recently found.

Grab the source: https://github.com/litecoin-project/litecoin
Windows (zip): https://github.com/downloads/litecoin-project/litecoin/litecoin-0.6.3-win32.zip
Windows (exe): https://github.com/downloads/litecoin-project/litecoin/litecoin-0.6.3b-win32-setup.exe
Linux (tgz, 32/64-bit): https://github.com/downloads/litecoin-project/litecoin/litecoin-0.6.3-linux.tar.gz
Mac OS X: https://github.com/downloads/litecoin-project/litecoin/litecoin-0.6.3-macosx.dmg

[smoothie]

Good Job coblee!

[pekv2]

As posted in the other thread, Thanks!

[ThiagoCMC]

AWESOME!! Good stuff!!

[ThiagoCMC]

Guys!

Let's build one of this: https://launchpad.net/~bitcoin/+archive/bitcoin/ to Litecoin?!

Litecoin Ubuntu PPA Stable Archive...    =P

Cheers!
Thiago

[tatsuchan]

Awesome.  Thank you for keeping up with us mac users too!

[pekv2]

Guys!

Let's build one of this: https://launchpad.net/~bitcoin/+archive/bitcoin/ to Litecoin?!

Litecoin Ubuntu PPA Stable Archive...    =P

Cheers!
Thiago

Was a long time user for Ubuntu, but as from I can tell, this would also work on Linux-Mint with the correct keys.

[pekv2]

Don't know if this is a bug.

This is how it happened.

Litecoin Client 0.6.3 Beta.

I have sent litecoins from the pool I mine at to my litecoin wallet that Litecoin Client 0.6.3 Beta handles.

I opened up the client about 20 minutes later. When the client opened, it showed my coins as unconfirmed on the main window, so I click on the transaction button to see how much time left, in the transaction window, it showed a green check mark for that transaction.

So, I then, closed the client, waited about a minute, then I ran the client again and then it finally popped to confirmed on the main window. By this time everything is ok, but as I ran the client, the client popped my coins from unconfirmed to confirmed on the main window, for a split second in red, the client said (Out of Sync] then disappeared.

But, atm, all seems fine besides that thing above I explained.

[pekv2]

Don't know if this is a bug.

This is how it happened.

Litecoin Client 0.6.3 Beta.

I have sent litecoins from the pool I mine at to my litecoin wallet that Litecoin Client 0.6.3 Beta handles.

I opened up the client about 20 minutes later. When the client opened, it showed my coins as unconfirmed on the main window, so I click on the transaction button to see how much time left, in the transaction window, it showed a green check mark for that transaction.

So, I then, closed the client, waited about a minute, then I ran the client again and then it finally popped to confirmed on the main window. By this time everything is ok, but as I ran the client, the client popped my coins from unconfirmed to confirmed on the main window, for a split second in red, the client said (Out of Sync] then disappeared.

But, atm, all seems fine besides that thing above I explained.

I've also noticed this issue and am looking into it.

Alright, cool.

Also, when sending ltc, even though it says 6 confirmations, Balance stays the same until the app is restarted.

I know that it just rolled out, I am sure there will be a few things to be ironed out.

Thanks!

[makomk]

I've also noticed this issue and am looking into it.

I'm running a recentish git version of the Bitcoin client and noticed the same thing happen on that a couple of days ago too, actually - started the client after having it closed for a while, and the balance on the summary page showed some bitcoins I'd received in the meantime as unconfirmed when the transaction had over 100 confirmations. Must be an upstream bug in the Bitcoin client.

[Coinbuck @ BTCLot]

Great job coblee. I've upgraded BTCLot Litecoin casino client.

[th3.r00t]

Don't know if this is a bug.

This is how it happened.

Litecoin Client 0.6.3 Beta.

I have sent litecoins from the pool I mine at to my litecoin wallet that Litecoin Client 0.6.3 Beta handles.

I opened up the client about 20 minutes later. When the client opened, it showed my coins as unconfirmed on the main window, so I click on the transaction button to see how much time left, in the transaction window, it showed a green check mark for that transaction.

So, I then, closed the client, waited about a minute, then I ran the client again and then it finally popped to confirmed on the main window. By this time everything is ok, but as I ran the client, the client popped my coins from unconfirmed to confirmed on the main window, for a split second in red, the client said (Out of Sync] then disappeared.

But, atm, all seems fine besides that thing above I explained.

I've also noticed this issue and am looking into it.

Alright, cool.

Also, when sending ltc, even though it says 6 confirmations, Balance stays the same until the app is restarted.

I know that it just rolled out, I am sure there will be a few things to be ironed out.

Thanks!

Same here.

[coblee]

A fix has been checked in. Testing right now and we will release another binary soon.

[coblee]

https://bitcointalk.org/index.php?topic=47417.msg1055265#msg1055265

[Graet]

Good work!
Thanks coblee

[-ck]

Code:

A fatal error occured. Litecoin can no longer continue safely and will quit.

EXCEPTION: 22DbRunRecoveryException       
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery       
litecoin in Runaway exception       

Double plus ungood.

[-ck]

Code:

A fatal error occured. Litecoin can no longer continue safely and will quit.

EXCEPTION: 22DbRunRecoveryException       
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery       
litecoin in Runaway exception       

Double plus ungood.

Then I tried building it for myself:

Code:

An error occured while setting up the RPC port 9332 for listening: open: Address family not supported by protocol

It seems any port I choose as a server for solo mining brings up that error.

[pooler]

Then I tried building it for myself:

Code:

An error occured while setting up the RPC port 9332 for listening: open: Address family not supported by protocol

It seems any port I choose as a server for solo mining brings up that error.

The only time I got that error was with an old Linux kernel that didn't support IPv6. I tried building bitcoind and it gave the same error.
Once I undefined USE_IPV6 and fixed bitcoinrpc.cpp to completely avoid IPv6, everything ran fine.

[LoWang]

I have the same error
And I had to delete folder database to make the previous version work again. That may happen to you too, so do this in that case.

[LoWang]

Oh but it crashed while synchronizing with a network