0.5 rc3 binaries available for testing

[Gavin Andresen]

If you can, please help sanity test Bitcoin 0.5 release candidate 3 binaries:
 https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.0/test/

Files and checksums are:

Code:

5077db912792ed1e341d0acecdd158717de97510  bitcoin-0.5.0rc3-linux.tar.gz
73e72328523482c91fceed6e676ec9e3b728a621  bitcoin-0.5.0rc3-macosx.dmg
6171be62a7dd18ce787889531525def80be13219  bitcoin-0.5.0rc3-win32-setup.exe
3c53c0008218ea5c4604984d07b5c5ddaaaf2287  bitcoin-0.5.0rc3-win32.zip

Linux and Windows binaries are created using the gitian-trusted/reproducible-build tool; the OSX binary was built by me.

I'll be writing up release notes this afternoon; assuming no 'show-stopper' bugs are found, these binaries will be the 0.5 release.

Please report bugs using the issue tracker at github:
  https://github.com/bitcoin/bitcoin/issues

 

[1713991395]

1713991395

[1713991395]

1713991395

[1713991395]

1713991395

[1713991395]

1713991395

[Bitsky]

Thanks for the update and progress Gavin!

Perhaps it would be possible to compile it the way Luke-Jr did? His rc1 ran fine on W2k. He mentioned only minor makefile changes.

Not sure what trouble BlueMatt et al are having, but I managed to build some Windows binaries. No guarantees, backup your wallet, etc...

Also, note that these aren't technically 0.5.0rc1, because I built with the very minor makefile changes made afterward (commits a1e0bb5a and e44a00ae) as well as having to hack up the build files more to make it work with my mingw setup (Gentoo crossdev i686-pc-mingw w/ GCC 4.4).

I didn't bother to build with UPnP support either cuz I was too lazy to cross-compile miniupnp (and I just needed the signmessage functionality).

• Static bitcoind 0.5.0rc1+
• Bitcoin-Qt 0.5.0rc1+ (libraries)
• Bitcoin-Qt 0.5.0rc1+ with signmessage_gui patch (libraries)

[Gavin Andresen]

Perhaps it would be possible to compile it the way Luke-Jr did? His rc1 ran fine on W2k. He mentioned only minor makefile changes.

Have you tried running rc3 on W2k?  I don't have a W2k machine to test on (I did sanity test rc2 on XP SP3), but I don't know of any reason it would fail.

[bulanula]

Hopefully I won't get my wallet deleted like with ScamCoin. Joking .

Great work dev. team ! Version 1.0.0 coming soon then ?

One thing I can report on Win7 x64 is much faster start up time compared to Luke-Jr's rc1 version so that is good.

Thanks !

[Bitsky]

Perhaps it would be possible to compile it the way Luke-Jr did? His rc1 ran fine on W2k. He mentioned only minor makefile changes.

Have you tried running rc3 on W2k?  I don't have a W2k machine to test on (I did sanity test rc2 on XP SP3), but I don't know of any reason it would fail.

I tried bitcoin-0.5.0rc3-win32.zip and got a freeaddrinfo/WS2_32.dll error message about a procedure entry point which wasn't found.

MSDN has some information about it: http://msdn.microsoft.com/en-us/library/ms737931(v=vs.85).aspx

I am well aware that W2k isn't supported by MS anymore, but if it just requires a tiny change it would be nice to have it rolled in. If there's a testbuild, I can try it; just PM me a link.

[Matt Corallo]

I tried bitcoin-0.5.0rc3-win32.zip and got a freeaddrinfo/WS2_32.dll error message about a procedure entry point which wasn't found.

MSDN has some information about it: http://msdn.microsoft.com/en-us/library/ms737931(v=vs.85).aspx

I am well aware that W2k isn't supported by MS anymore, but if it just requires a tiny change it would be nice to have it rolled in. If there's a testbuild, I can try it; just PM me a link.

The Win2k issues are a result of miniupnpc's compilation.  In previous releases, the binary release of miniupnpc was used, meaning we had no control over this.  However, with 0.5 miniupnpc is being built from source in the build scripts.  All that should need changed is adding a #include WSPiApi.h to the miniupnpc source files (and get a copy of WSPiApi.h from Windows Platform SDK and drop that in an include directory) at build-time, but I haven't had the chance to do that and when I asked a couple days ago on #bitcoin for anyone who was willing to help, all I got was a bunch of people asking why bother?
In any case, if I get the chance I'll try to whip something up, otherwise it might have to wait till 0.6...

[finway]

works fine for me. 
@win7 32bit

[shads]

Ubuntu 10.04 64 bit.

~/.bitcoin from a 0.3.24 vanilla build.

Started bitcoin-qt with -server and -upnp

It loaded to the point where the frame of the main window appeared without anything inside it then crashed.

Removed -server -upnp from the startup command and it worked.


I assume this was because I'd recently removed rpcuser/pw from bitcoin.conf.

Confusing if you're reasonably new to bitcoin though.

[fornit]

works fine for me. 
@win7 32bit

#2
win7 64bit

some minor issues:
- in the overview tab, when i hover over recent transactions, i get tooltips that consist of entirely black boxes.
- sorting by address in the transaction tab is case sensitive, leading to very weird results like A < BUT < Bot < bat < x
- transaction filter is also case sensitive
- date selection box in transaction filter is white on white, which not only makes looks bad but also makes it very hard to distinguish between black and grey dates.
- dialog boxes have a question mark button which as far as i can tell does nothing in any box.
- german translation is incomplete and in some cases wrong or ackward (luckily nothing that can be misunderstood)

[slothbag]

Win7 32bit

Runs well for me, consuming about 50mb of memory on average (previous version was around 40mb), got as high as 70mb.
Takes only a few seconds to load with an empty wallet, about 30 - 40 seconds with a wallet containing a few hundred addresses
Socks proxy mode working well, direct connection also working well

One issue I found, I was running "bitcoin-qt.exe -server" and then did a "bitcoind.exe signmessage blah blah" and the bitcoin-qt.exe crashed out.  Then issuing a "bitcoind.exe signmessage <correct address> test" caused bitcoin-qt.exe to lock up.  I had not unlocked my wallet, so maybe that had something to do with, once the wallet is unlocked it appears to behave a bit better.