[MOJO] MOJOv3 has been taken over by new devs - page 24.

EBK1000

legendary

Activity: 1148

Merit: 1000

A Wound in Eternity

Quote from: alexxynn on October 10, 2016, 08:28:29 AM

I have the same problem: transactions aren't confirmed or confirmed very long.

I am aware of this problem and it has been highlighted so it's being considered. I have a workaround that works in some instances. I know it's not ideal but...if you have problems sending, it helps to restart the wallet and leave it locked and then make the transaction. If the transaction appears to get stuck open the wallet for staking and as you get a stake reward the transaction is normally confirmed. As I said, not ideal but works for me on Mac OSX qt.

I agree that more PR should be done and I would welcome any ideas.

alexxynn

sr. member

Activity: 381

Merit: 250

I have the same problem: transactions aren't confirmed or confirmed very long.

hagie

hero member

Activity: 792

Merit: 501

Sending coins from my controller wallet to livecoin takes at least 24h .. often they get stuck and never transfered ..

is there a fix planed for this problem ?

regards

Limx Dev

copper member

Activity: 2324

Merit: 1348

drays

legendary

Activity: 2576

Merit: 1073

Even with wallet version 2.4.0.0 the wallet on my PC cannot find a single stable connection - connections just appear and disappear immediately.

Is there anything useful in this log:

Code:

2016-10-09 23:35:01 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:01 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:02 socket recv error 10054
2016-10-09 23:35:03 socket recv error 10054
2016-10-09 23:35:04 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:04 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:04 socket recv error 10054
2016-10-09 23:35:05 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:05 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:06 socket recv error 10054
2016-10-09 23:35:06 socket recv error 10054
2016-10-09 23:35:07 socket recv error 10054
2016-10-09 23:35:08 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:08 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:08 socket recv error 10054
2016-10-09 23:35:10 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:10 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:10 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:10 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:23 socket recv error 10054
2016-10-09 23:35:34 CheckStakeKernelHash() : using modifier 0x619a43beed457013 at height=154441 timestamp=2016-09-24 10:37:42 UTC for block from timestamp=2016-09-23 17:34:08 UTC
2016-10-09 23:35:34 CheckStakeKernelHash() : check modifier=0x619a43beed457013 nTimeBlockFrom=1474652048 nTimeTxPrev=1474652048 nPrevout=1 nTimeTx=1476056128 hashProof=43fb92e02552963661cb4351ba01eab5aae68625f139b99ac967f18fd76febec
2016-10-09 23:35:34 CheckStakeKernelHash() : using modifier 0x619a43beed457013 at height=154441 timestamp=2016-09-24 10:37:42 UTC for block from timestamp=2016-09-23 17:34:08 UTC
2016-10-09 23:35:34 CheckStakeKernelHash() : check modifier=0x619a43beed457013 nTimeBlockFrom=1474652048 nTimeTxPrev=1474652048 nPrevout=2 nTimeTx=1476056128 hashProof=46b8933c8c37655f6309fd12134eaea2faaaf835a0506c9254f886996feab28c
2016-10-09 23:35:34 CheckStakeKernelHash() : using modifier 0x619a43beed457013 at height=154441 timestamp=2016-09-24 10:37:42 UTC for block from timestamp=2016-09-21 15:02:56 UTC
2016-10-09 23:35:34 CheckStakeKernelHash() : check modifier=0x619a43beed457013 nTimeBlockFrom=1474470176 nTimeTxPrev=1474470176 nPrevout=2 nTimeTx=1476056128 hashProof=41b8d9d113d604e37b7f8d064f1ce30e95e6139366c1e436a49b3e84b3d1086d
2016-10-09 23:35:36 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:36 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:36 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:36 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:37 socket recv error 10054
2016-10-09 23:35:37 socket recv error 10054
2016-10-09 23:35:38 socket recv error 10054
2016-10-09 23:35:39 socket recv error 10054
2016-10-09 23:35:40 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:40 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:40 socket recv error 10054
2016-10-09 23:35:41 socket recv error 10054
2016-10-09 23:35:47 socket recv error 10054
2016-10-09 23:35:48 socket recv error 10054
2016-10-09 23:35:49 socket recv error 10054
2016-10-09 23:35:49 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:49 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:50 socket recv error 10054
2016-10-09 23:35:51 socket recv error 10054
2016-10-09 23:35:52 socket recv error 10054
2016-10-09 23:35:52 socket recv error 10054
2016-10-09 23:35:53 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:53 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:54 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:54 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:35:55 socket recv error 10054
2016-10-09 23:35:55 socket recv error 10054
2016-10-09 23:35:56 socket recv error 10054
2016-10-09 23:35:58 socket recv error 10054
2016-10-09 23:35:58 socket recv error 10054
2016-10-09 23:35:59 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:35:59 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:36:00 socket recv error 10054
2016-10-09 23:36:00 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:36:00 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:36:07 socket recv error 10054
2016-10-09 23:36:07 socket recv error 10054
2016-10-09 23:36:08 socket recv error 10054
2016-10-09 23:36:09 socket recv error 10054
2016-10-09 23:36:10 socket recv error 10054
2016-10-09 23:36:17 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:36:17 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:36:17 socket send error 10038
2016-10-09 23:36:17 socket recv error 10054
2016-10-09 23:36:18 socket recv error 10054
2016-10-09 23:36:19 socket recv error 10054
2016-10-09 23:36:20 socket recv error 10054
2016-10-09 23:36:20 socket recv error 10054
2016-10-09 23:36:21 socket recv error 10054
2016-10-09 23:36:22 socket recv error 10054
2016-10-09 23:36:22 socket recv error 10054
2016-10-09 23:36:24 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:36:24 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:36:24 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:36:24 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:36:25 socket recv error 10053
2016-10-09 23:36:26 socket recv error 10054
2016-10-09 23:36:38 socket recv error 10054
2016-10-09 23:36:39 socket recv error 10054
2016-10-09 23:36:40 socket recv error 10054
2016-10-09 23:36:41 socket recv error 10054
2016-10-09 23:36:41 socket recv error 10054
2016-10-09 23:36:53 socket recv error 10054
2016-10-09 23:36:54 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:36:54 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:36:55 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:36:55 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:36:55 socket recv error 10054
2016-10-09 23:36:56 socket recv error 10054
2016-10-09 23:36:57 socket recv error 10054
2016-10-09 23:36:58 socket recv error 10054
2016-10-09 23:36:58 socket recv error 10054
2016-10-09 23:36:59 socket recv error 10054
2016-10-09 23:37:00 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:00 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:01 socket recv error 10054
2016-10-09 23:37:01 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:01 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:08 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:08 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:09 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:09 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:10 socket recv error 10054
2016-10-09 23:37:10 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:10 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:11 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:11 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:17 socket recv error 10054
2016-10-09 23:37:18 socket recv error 10054
2016-10-09 23:37:19 socket recv error 10054
2016-10-09 23:37:20 socket recv error 10054
2016-10-09 23:37:22 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:22 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:22 socket recv error 10054
2016-10-09 23:37:29 socket recv error 10054
2016-10-09 23:37:30 socket recv error 10054
2016-10-09 23:37:30 socket recv error 10054
2016-10-09 23:37:31 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:31 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:32 socket recv error 10054
2016-10-09 23:37:50 socket recv error 10054
2016-10-09 23:37:51 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:51 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:51 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:51 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:52 socket recv error 10054
2016-10-09 23:37:53 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:37:53 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:37:53 socket recv error 10054
2016-10-09 23:37:54 socket recv error 10054
2016-10-09 23:37:56 socket recv error 10054
2016-10-09 23:37:57 socket recv error 10054
2016-10-09 23:37:58 socket recv error 10054
2016-10-09 23:38:05 socket recv error 10054
2016-10-09 23:38:06 socket recv error 10054
2016-10-09 23:38:06 socket recv error 10054
2016-10-09 23:38:07 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:38:07 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:38:08 socket recv error 10054
2016-10-09 23:38:09 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:38:09 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:38:10 socket recv error 10054
2016-10-09 23:38:11 socket recv error 10054
2016-10-09 23:38:22 socket recv error 10054
2016-10-09 23:38:23 socket recv error 10054
2016-10-09 23:38:30 socket recv error 10054
2016-10-09 23:38:30 socket recv error 10054
2016-10-09 23:38:31 socket recv error 10054
2016-10-09 23:38:32 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:38:32 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:38:32 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:38:32 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:38:33 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:38:33 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:38:34 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:38:34 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:38:41 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:38:41 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:38:41 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:38:41 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:38:42 socket recv error 10054
2016-10-09 23:38:43 socket recv error 10054
2016-10-09 23:38:44 socket recv error 10054
2016-10-09 23:38:44 socket recv error 10054
2016-10-09 23:38:45 socket recv error 10054
2016-10-09 23:38:46 socket recv error 10054
2016-10-09 23:38:52 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:38:52 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:38:53 socket recv error 10053
2016-10-09 23:38:53 socket recv error 10054
2016-10-09 23:38:54 socket recv error 10054
2016-10-09 23:39:00 socket recv error 10054
2016-10-09 23:39:01 socket recv error 10054
2016-10-09 23:39:02 socket recv error 10054
2016-10-09 23:39:02 socket recv error 10054
2016-10-09 23:39:04 socket recv error 10054
2016-10-09 23:39:10 socket recv error 10054
2016-10-09 23:39:11 socket recv error 10054
2016-10-09 23:39:12 socket recv error 10054
2016-10-09 23:39:12 socket recv error 10054
2016-10-09 23:39:21 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:39:21 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:39:21 socket recv error 10054
2016-10-09 23:39:27 socket recv error 10054
2016-10-09 23:39:29 socket recv error 10054
2016-10-09 23:39:35 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-10-09 23:39:35 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:39:36 socket recv error 10054
2016-10-09 23:39:36 socket recv error 10054
2016-10-09 23:39:37 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-10-09 23:39:37 ProcessMessage(version, 101 bytes) FAILED
2016-10-09 23:39:38 socket recv error 10054

Wasn't this version supposed to fix this issue? It looks like I have to wait for MOJOv3, for this to be fixed... Sad

hagie

hero member

Activity: 792

Merit: 501

We need news - the coin need to raise awareness.

Where is the roadmap for the coin ? Where is the PR ?

regards

Dxt

hero member

Activity: 532

Merit: 500

Vote ratio 1:1 (1 for 1 swap - no reduction). The current number is optimal, reduction of no advantage.

CryptoHobo

legendary

Activity: 1050

Merit: 1000

Quote from: EBK1000 on October 02, 2016, 12:27:30 PM

CryptoID block explorer has been updated to v2.4 and appears to show connected nodes correctly.

PLS UPDATE TO V2.4 BEFORE BLOCK 200,000
V2.3 AND OLDER W/ PROTOCOL <90001 WILL BE LOCKED OUT FROM THE NETWORK
IF YOU RUNNING OLDER SOFTWARE PLEASE UPDATE ASAP

poswallet still using v2.3.0.0-61402 i'll send them a mail

dsutil

member

Activity: 116

Merit: 10

Voted 1:1 as I don't see any benefits in reduce the number of coins.

Haunebu81

hero member

Activity: 525

Merit: 500

Quote from: bumbacoin on October 04, 2016, 12:36:22 AM

Quote from: bumbacoin on October 03, 2016, 10:03:22 PM

Quote from: Haunebu81 on October 03, 2016, 03:35:01 PM

Quote from: Haunebu81 on October 03, 2016, 07:31:59 AM

Are there additional dependencies that need to be installed when using mojocoind 2.4 on Ubuntu 14.04? I'm not in front of my rig right now, but I was getting a bunch or errors (I posted it in slack).

If so, what's the apt-get link?

I'm getting the following error:

/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found

Can anyone help? I'm on Ubuntu 14.04.

are you using the version i compiled ??
i've noticed i've compiled it on ubuntu 16.
possibly 14.04 doesnt have that version or is looking in the wrong spot.

i'll have a look and see what i can do. possibly recompile for ubuntu 14

try this version.
compiled on ubuntu 14.04. https://drive.google.com/file/d/0B5j8d4FSc7draEgwc0pYa2dXTkk/view?usp=sharing

the problem seemed to be that that system lib was not backward compatible.
haha hope no-one comes along with ubuntu 12 ..

Works now. Thanks!

hagie

hero member

Activity: 792

Merit: 501

voted for 1:1 .. I see no gain in reducing the supply ..

regards

bumbacoin

legendary

Activity: 1638

Merit: 1036

Quote from: bumbacoin on October 03, 2016, 10:03:22 PM

Quote from: Haunebu81 on October 03, 2016, 03:35:01 PM

Quote from: Haunebu81 on October 03, 2016, 07:31:59 AM

Are there additional dependencies that need to be installed when using mojocoind 2.4 on Ubuntu 14.04? I'm not in front of my rig right now, but I was getting a bunch or errors (I posted it in slack).

If so, what's the apt-get link?

I'm getting the following error:

/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found

Can anyone help? I'm on Ubuntu 14.04.

are you using the version i compiled ??
i've noticed i've compiled it on ubuntu 16.
possibly 14.04 doesnt have that version or is looking in the wrong spot.

i'll have a look and see what i can do. possibly recompile for ubuntu 14

try this version.
compiled on ubuntu 14.04. https://drive.google.com/file/d/0B5j8d4FSc7draEgwc0pYa2dXTkk/view?usp=sharing

the problem seemed to be that that system lib was not backward compatible.
haha hope no-one comes along with ubuntu 12 ..

bumbacoin

legendary

Activity: 1638

Merit: 1036

Quote from: Haunebu81 on October 03, 2016, 03:35:01 PM

Quote from: Haunebu81 on October 03, 2016, 07:31:59 AM

Are there additional dependencies that need to be installed when using mojocoind 2.4 on Ubuntu 14.04? I'm not in front of my rig right now, but I was getting a bunch or errors (I posted it in slack).

If so, what's the apt-get link?

I'm getting the following error:

/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found

Can anyone help? I'm on Ubuntu 14.04.

are you using the version i compiled ??
i've noticed i've compiled it on ubuntu 16.
possibly 14.04 doesnt have that version or is looking in the wrong spot.

i'll have a look and see what i can do. possibly recompile for ubuntu 14

d-trix

sr. member

Activity: 459

Merit: 250

Quote from: drays on October 03, 2016, 03:31:31 PM

I don't see a single reason for changing the coin supply at this stage. There should be a reason for a change, right?

BTW, there will not be any profit in reducing the coin supply either - neither short term, nor long term. If you reduce the supply twice, the price will increase 2 times, but you will have two times less coins to sell, so the result is the same.

Voted for 1:1, because of no reason for change. Could actually vote for any other option too, because I believe the coin supply is not important at all for MOJO on this stage. The supply is important for coins which have clear use case. For MOJO this is still unclear.

Does anyone see a single reason for a supply change?

None at all imho, that's why I fully agree not to change the previous coin supply and should remain the same.

kenobius

legendary

Activity: 1650

Merit: 1033

I think Ratio 1:1 (1 for 1 swap - no reduction) is the best choice. Other options will confuse users.

Haunebu81

hero member

Activity: 525

Merit: 500

Quote from: Haunebu81 on October 03, 2016, 07:31:59 AM

Are there additional dependencies that need to be installed when using mojocoind 2.4 on Ubuntu 14.04? I'm not in front of my rig right now, but I was getting a bunch or errors (I posted it in slack).

If so, what's the apt-get link?

I'm getting the following error:

/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found

Can anyone help? I'm on Ubuntu 14.04.

drays

legendary

Activity: 2576

Merit: 1073

I don't see a single reason for changing the coin supply at this stage. There should be a reason for a change, right?

BTW, there will not be any profit in reducing the coin supply either - neither short term, nor long term. If you reduce the supply twice, the price will increase 2 times, but you will have two times less coins to sell, so the result is the same.

Voted for 1:1, because of no reason for change. Could actually vote for any other option too, because I believe the coin supply is not important at all for MOJO on this stage. The supply is important for coins which have clear use case. For MOJO this is still unclear.

Does anyone see a single reason for a supply change?

cjmining

hero member

Activity: 586

Merit: 500

Waiting for my coins to rise !!

It's difficult to just say reduce, or not, the supply of the coin. Most people will pick which they think will be best for them, ie increase the price so they can sell at a profit. What would be the best choice for the coin in the long run ? the best choice for the coin will also be the best choice for the long term price of the coin. Reducing the coin supply may have a quick effect, suitable for those wishing to sell quickly, but will it be the best option for the long term benefit of the coin and the people that want to hold the coin ? I would like to see some arguments for, and against, coin reduction or not before i can make any judgement.

Also i would not want the coin reduced just because people vote for it. There are alot of people that hold Mojo, most of them have very few and will vote for the option that allows them to make the quickest profit. If the total is to be changed, it should get the backing of the people with the majority of the coins not just the most votes.

Finally. What is the problem with the MOJO wallet ? looking at this from an old man that knows nothing about coding point of view? I have been in crypto for about 3 years and have seen many coins come, and go, over that time but have never seen one with the constant wallet problems that seem to persist with this coin. There are simple coins out there and some more complex coins out there but none seem to have the wallet problems that Mojo does. It surely has to be a turnoff to anyone reading this forum if they are looking to buy Mojo. I have held this coin for what seems an eternity, and keep picking up a few more when the price dips. It would be nice to see all the issues put to bed and the coin start to do what it set out to do.

Cheers....

Jack Liver

legendary

Activity: 1981

Merit: 1039

voted for 1:1 ratio i'm cool with the other ones but 1:10 it's definetly too low

Haunebu81

hero member

Activity: 525

Merit: 500

Are there additional dependencies that need to be installed when using mojocoind 2.4 on Ubuntu 14.04? I'm not in front of my rig right now, but I was getting a bunch or errors (I posted it in slack).

If so, what's the apt-get link?

Topic: [MOJO] MOJOv3 has been taken over by new devs - page 24. (Read 167315 times)