Hmm, I'm surprised this issue hasn't been fixed yet with a proper 5.2.0 package in the repositories.. hopefully we will see something soon. Anyone know an ETA?
Hmm, I'm surprised this issue hasn't been fixed yet with a proper 5.2.0 package in the repositories.. hopefully we will see something soon. Anyone know an ETA?