Check this thread for compiling it yoursef: www.indilib.org/forum/general/9748-build...-from-git.html#71737

I am a bit frustrated at the moment. I thought I read where KStars 3.5.2 was part of Astroberry, so I expected it to be there with the latest Astroberry install I did. It was not. Thinking maybe I needed to update/upgrade, I the the sudo apt update and that went fine. I then did sudo apt upgrade, and that pretty much wiped my sdcard back to 4 green blinks and almost nothing on the sdcard. Having to start all over again. 

For now, I'll look on the bright side and say I needed the experience anyway.

I updated my Astroberry (Sudo apt-get update && sudo apt-get upgrade) and I now have KStars 3.5.2
I was hoping for KStars 3.5.3

   

KStars 3.5.3 is not available yet on Astroberry. It is promised soon?

There seems to be an issue with KStars 3.5.3 on RPi it does not include Ekos even if you compile from source.

A fix is still awaited.

Just wondering what extras we’re anticipating with 3.5.3?
I been running Astroberry 2.0.3 since it was launched, on two Astro rigs. I updated each a couple of weeks ago (sudo apt update followed by sudo apt full-upgrade to make sure I caught any dependencies). I have been pretty happy with the resulting upgrade to version (or perhaps sub-version of) 3.5.2 which does include the updated polar alignment vector errors that an earlier post was mentioning. 
I have had more than one failed microSD card over the 2+ years I’ve been using Raspberry Pi 4s, and now run only from SSDs for speed, size and reliability.

The current version of INDI on the latest Astroberry has a bug in the Nexdome Driver.  It has been fixed in version 1.9.0.
Does anyone know when Astroberry will get the new updated INDI and KStars (3.5.3)?

Peter

It might be a while.

Astroberry is only updated infrequently.

I love chasing the lastest version of softwares but Kstars really taught me not to. 3.4.2 worked fine for me and when I started using 3.4.3, 3.5.0 and all the way to 3.5.3, I had bad night almost every time.

I agree, I feel I should have two images, one for testing the latest version, and another for trying to do astronomy with. There are far too many glitches / changes of operation with version updates for both INDI and Kstars that doing regular updates to something that already works isn't such a good idea. Especially when imaging time is limited.

On my SBC, I have an apt installed version which I refrain myself to upgrade and I compiled from source to try new features like the new PA procedure.

I agree I now have a working version of Kstars/Ekos (+Indi) which I don't change and another testing version which I can download the latest daily releases and compile from scratch. There is a thread on here about it using a script and it works perfectly.

indilib.org/forum/general/9748-build-kst...-from-git.html#71973

It would be great to have something like a Long Term Support distribution,