If you don’t mind backing up CSources2 v600.840-2 & below using the Backup feature, then update CSources2, then press Restore. You will not need to remove the postrm file.
But, it is much faster to remove the postrm then update CSources2 to v600.840-3.
If you are running v600.840-3 and up, IGNORE THIS BLOG & update.
I will explain a little deeper.
An issue with versions 600.840-2 & below was discovered, which when updating CSources2, forced certain files to remove themselves before the update was complete. When that happened CSources2 was tricked into believing it was a fresh install and started from scratch “That is not what I intended”. If you have v600.840-2 & below currently installed, it is recommended to remove the postrm file that version already installed, before updating.
- Always Backup an app/tweak before updating if possible.
- After Backing up, Close CSources2 completely.
- Using iFile etc, Go to : /private/var/lib/dpkg/info/
- Remove/Delete : com.dirtybeans.csources2.postrm
- Do not run/open CSources2.
- Open Cydia / Refresh / Update CSources2.
- Now you can Run CSources2, your sources will be as they were before update.
- As always, its best to perform a Backup. š
Removing the postrm before upgrading to v-3 allows the upgraded app to open CSources2 data as it was before the update, instead of an empty list. Removing the postrm file will allow you to retain your current sources, and you won’t need to press Restore after you update CSources2.
(This has nothing to do with restoring/upgrading your device).
If you do not delete the postrm file then CSources2 will remove certain files when you upgrade to 600.840-3. In that case you would have to press Restore to return your previous CSources2 sources.
This is not major as long as has been stressed in these docs and app, is to BACKUP.
If you don’t delete the postrm file, backup CSources2 using Backup feature, then you can upgrade to 600.840-3 you will have to press Restore for the sources to return.
Some users did not mind pressing restore after the upgrade, because they made a backup. I personally made a note for this to be removed, but was missed. The hassle is having Restore gather all the info that was already present before the update.
CSources2 was not intended to force a restore after updating (This is in error).
Versions after installing 600.840-3 will not have this issue.
CSources2 