What repositories updated to solve issues found by libccoin?

[gigabytecoin]

If I build namecoind from source located at https://github.com/namecoin/namecoin will I be contributing to solving the problem outlined by libcoin?

It doesn't really matter which namecoin client I use to hold my coins, does it?

vinced/namecoin
khalahan/namecoin
namecoin/namecoin
namecoin-qt/namecoin-qt

Are all up to date now?

What's stopping somebody with an older client from re-registering bitcoin.bit or any other registered .bit domain after the Dec 15th hard fork?

[snailbrain]

If I build namecoind from source located at https://github.com/namecoin/namecoin will I be contributing to solving the problem outlined by libcoin?

It doesn't really matter which namecoin client I use to hold my coins, does it?

vinced/namecoin
khalahan/namecoin
namecoin/namecoin
namecoin-qt/namecoin-qt

Are all up to date now?

What's stopping somebody with an older client from re-registering bitcoin.bit or any other registered .bit domain after the Dec 15th hard fork?

https://bitcointalk.org/index.php?topic=322939.0

Just these:
namecoinq/namecoinq
namecoin-qt/namecoin-qt
namecoin/namecoin

it shouldn't get accepted

[cassini]

Just these:
namecoinq/namecoinq
namecoin-qt/namecoin-qt
namecoin/namecoin

namecoinq/namecoinq:
static const int VERSION = 37200;

namecoin-qt/namecoin-qt:
static const int VERSION = 37200;

namecoin/namecoin:
static const int VERSION = 35100;

[gigabytecoin]

It is a bit disturbing have so many "official" repositories.

[snailbrain]

Namecoin-qt and namecoinq are the same - Newest

namecoin/namecoin is the old daemon with just the hardfork patch.

They all have the patch.