Signed-off-by: Anna Vyalkova <cyber+gen...@sysrq.in>
---
Related to this version bump and unmask:
https://archives.gentoo.org/gentoo-proxy-maint/message/d86352b4ebad8c4ddd14fcd8ce37162f

 ...27-upgrade-to-net-news_rssguard-4_0.en.txt | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 
2021-10-27-upgrade-to-net-news_rssguard-4_0/2021-10-27-upgrade-to-net-news_rssguard-4_0.en.txt

diff --git 
a/2021-10-27-upgrade-to-net-news_rssguard-4_0/2021-10-27-upgrade-to-net-news_rssguard-4_0.en.txt
 
b/2021-10-27-upgrade-to-net-news_rssguard-4_0/2021-10-27-upgrade-to-net-news_rssguard-4_0.en.txt
new file mode 100644
index 0000000..35971f0
--- /dev/null
+++ 
b/2021-10-27-upgrade-to-net-news_rssguard-4_0/2021-10-27-upgrade-to-net-news_rssguard-4_0.en.txt
@@ -0,0 +1,29 @@
+Title: net-news/rssguard-4.0 upgrade
+Author: Anna Vyalkova <cyber+gen...@sysrq.in>
+Posted: 2021-10-27
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: <net-news/rssguard-4.0
+
+RSS Guard database files created by RSS Guard version 3.9.x are
+incompatible with RSS Guard version 4.0 or later [0].
+
+Configuration file (config.ini) is fully backwards compatible according
+to the upstream. You can save it (File -> Backup settings) before an
+upgrade and restore it later (File -> Restore settings).
+
+There is no reliable way to automate the database format conversion, so
+action from the user is required before an upgrade can take place.
+
+The first option would be to export your feeds as an OMPL file
+(Accounts -> Export feeds) before an upgrade and import them later
+(Account -> Import feeds).
+
+The second option would be to manually update your database.db file to
+4.x.x format following a guide by the upstream developer [1].
+
+Keep in mind that application data directory has been renamed from
+"~/.config/RSS Guard" to "~/.config/RSS Guard 4".
+
+[0] https://github.com/martinrotter/rssguard/releases/tag/4.0.0
+[1] 
https://github.com/martinrotter/rssguard/blob/master/resources/docs/Documentation.md#migratt
-- 
2.33.1


Reply via email to