The repository has kstars 3.5 but in my case I had to perform distro update. After using
apt-get dist-upgrade, I got the newest kstars with no problems.

did you get 3.5.1 already? Or 3.5.0?

Tried to run update just now to see if 3.5.1 was available, but hit an error:

E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?

(yes, I used sudo) I have successfully updated in the past.
Rebooted the pi, same result. Suggestions?

This error occurs when there is already one instance of the updater running. However, installation should work after reboot (you kill it),
But also could be a daemon which is started at boot,,, Please, check which applications are running with the task manager and if you see something related to program/dist updating, kill it.

Thanks for the reply. Nothing jumps out at me, but I am not familiar with what should or should not be running at startup.

I do not see anything that could be getting the lock...
Sorry, out of ideas

The usual culprit on Ubuntu is unattended-upgrade. But I'm not familiar with Astroberry and that might not exist or has been disabled.

Little snippets of *NIX come back to me in a foggy haze sometimes. I used sudo -s and then separately apt-get update then apt-get upgrade. That worked.

Still KStars 3.5.0 though, so I'll need to do it again, I guess in a few days

Hello,

The error with the packaging DB getting locked usually occurs within 60-70 secs after boot up. I wait 2-3 minutes for Raspbian OS to finish its health checks before checking for updates. The lock is supposed to be temporary. As for KSTARS not updating, the AstroBerry canonical list is limited to few libraries. This is to ensure that the paradigm of AstroBerry doesn’t get so messed up that Kaczorek spends a long time fixing.

I added the canonical libraries of KSTARS Bleeding, INDI, and a Raspbian. That was it. Raspbian is nothing like Ubuntu. Ubuntu mixes i386 with ARMFH. For example, under Ubuntu, a Raspberry kernel update will never install because a symbolic link it tries to create is on the FAT32 side of Raspbian. I sought support and was told this kernel is for i386 and who is Raspberry?

Hi Arado,
so you did the following in the astroberry installation?

What canonical library for raspbian did you include? I'm not so familiar with Raspberry Pi OS/Raspbian...

Thank you

Hello,

Yes. These two repositories were what I add. The Raspbian was specifically for BIOS and Firmware. I noticed several needed updating before Raspbian and AstroBerry were at peace with each other.

do you have the name of the raspbian repository I have to add? Sorry, but I'm more familiar with opensuse