886 outlines an issue where the toltecctl reenable code just changes the architecture in /opt/lib/opkg/status to update the os portion to the current one. It doesn't take into account if the new packages are not the same rm portion. e.g. rm2os3 -> rm2os2 instead of rmallos2.
This works around the current issue with toltec-deletions. A better solution in toltecctl will need to be done in the future.
886 outlines an issue where the
toltecctl reenablecode just changes the architecture in/opt/lib/opkg/statusto update the os portion to the current one. It doesn't take into account if the new packages are not the same rm portion. e.g. rm2os3 -> rm2os2 instead of rmallos2.This works around the current issue with toltec-deletions. A better solution in toltecctl will need to be done in the future.