Working around Beaglebone opkg upgrade bug

I posted a problem on the Angstrom-users list but have had no replies.
Perhaps the list is inactive:
http://lists.linuxtogo.org/pipermail/angstrom-distro-users/2012-October/004118.html

Basically running "opkg update && opkg upgrade" on the beagleBONE
doesn't work. It appears to break various //var/lib/opkg/info/*.list
files.

As a result to keep internet facing services up to date I had to do a
work-around with "opkg --force-reinstall install openssh". With this
you have to get the exact package match; "opkg --force-reinstall
install ssh" doesn't work.

The force reinstall will download the latest package according to any
changes resulting from "opkg update".

I hope this helps someone.

If you are running dropbear you'll get a conflict. I don't know how to
do this change from dropbear to openssh without losing remote
connectivity. Running a screen session might work but if the
changeover fails you might end up reimaging the sdcard image to the
sdcard. Might be better to stick with dropbear until you come across
functionality in openssh you need.

Yep. A hot upgrade of Angstrom on the BB usually die on the middle on my Bones with disk full. Usually a retry of the opkg upgrade finish the job.

Others just download the latest image (not the best since you loose your config)

I posted a problem on the Angstrom-users list but have had no replies.
Perhaps the list is inactive:
http://lists.linuxtogo.org/pipermail/angstrom-distro-users/2012-October/004118.html

I’ve heard things like contact TI to let them known USB is broken we could apply “contact your Angstrom support to tell them Angstrom is broken ;)” or basically we can use Debian/Ubuntu/Gentoo or another SoC, sad but nobody is being paid to support BB or Angstrom.

Basically running “opkg update && opkg upgrade” on the beagleBONE
doesn’t work. It appears to break various //var/lib/opkg/info/*.list
files.

As a result to keep internet facing services up to date I had to do a
work-around with “opkg --force-reinstall install openssh”. With this
you have to get the exact package match; “opkg --force-reinstall
install ssh” doesn’t work.

The force reinstall will download the latest package according to any
changes resulting from “opkg update”.

I hope this helps someone.

Thanks for the tip :slight_smile: