From 11:00 PM CST Friday, Feb 14th - 6:30 PM CST Saturday, Feb 15th, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CST Friday, Feb 14th - 6:30 PM CST Saturday, Feb 15th, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
12-22-2016 04:45 PM
Has anyone been able to get the opkg --force-downgrade option to work? I've tried all sorts of variations without success. The only way I can revert a package to a previous version is by uninstalling it, restricting access to the only the specific version I want (either by removing the package from the repo or directing the sbRIO to another repo that doesn't have the updated version), and reinstalling the package. I'm hoping somebody has a better way.
12-23-2016 02:46 AM
I got it down-gradable by directly using the .ipk file name with --force-downgradable.
Not sure how "--force-downgradable" command works with all the packages/Repo at one time
12-23-2016 12:14 PM - edited 12-23-2016 12:16 PM
[Deleted duplicate]
12-23-2016 12:15 PM
Thanks Bhaskar. To make sure I understand you correctly, these are the steps:
I was hoping to find a way to retrieve the prior package from the repository and downgrade it all in one step, much like an upgrade works. This adds more complexity when trying to automate the process.
12-24-2016 09:08 AM
Usually, the feeds put up by NI only have one version of a particular software package, so there's usually nothing to downgrade to. Could you share your use-case where you're interested in automating downgrading software packages?
12-24-2016 03:06 PM
We are setting up our own opkg repository to deploy our software--as packages--to our devices around the world. Our operations team has to be able to roll back to a previous version in case the updated version doesn't work as expected on that particular device.