GNOME Bugzilla – Bug 472934
Support for Liferea 1.4
Last modified: 2018-07-03 09:56:47 UTC
Liferea 1.4 uses another method of storing its feeds (sqlite) which results in beagle not being able to index liferea feeds at the moment.
This will be hard to do ... its very hard, mostly impossible, to track changes in sqlite without app support.
(In reply to comment #1) > This will be hard to do ... its very hard, mostly impossible, to track changes > in sqlite without app support. > In that case the now defunct liferea backend better be removed.
When was liferea-1.4 released ? Do most distributions (current release and last release) ship liferea >= 1.4 ?
(In reply to comment #3) > When was liferea-1.4 released ? Do most distributions (current release and > last release) ship liferea >= 1.4 ? Liferea 1.4.0 was relased August 31 2007. Since newer versions of beagle and liferea will equally go into the development branches of the distributions rather than being uploaded into existing stable releases, I don't believe that a situation will incur where a new beagle meets an old liferea. I've also submitted a bug report to liferea http://sourceforge.net/tracker/index.php?func=detail&aid=1886967&group_id=87005&atid=581684 But since liferea is maintained by a single developer, I would not have high hopes to have them fixed it, soon. 2007-08-31 Lars Lindner <lars.lindner@gmail.com> Version 1.4.0 (Stable) Changes Compared to 1.2: * Comment feed support: auto-downloading of comments. * Sqlite3 database backend for feed content storage. * Improved proxy support (better no-proxy support). * Duplicate headlines detection. * Automatic browser support selection (removed preference) * Dropped proprietary popup code in favour of libnotify solution. * Improved DBUS support, some new methods. * Added support for gwget support as download tool. (patch from Stephan Maka) Fixes since 1.4-RC3:
This is the response from the liferea developer, see https://sourceforge.net/tracker/index.php?func=detail&aid=1886967&group_id=87005&atid=581684 Maybe his suggestions are helpful: "While I do not think it is impossible I also cannot say how to do it exactly because I don't know about the Beagle indexing (and personally I do not use it). Also I want to note that the cache files are internal interfaces not to be relied on (disclaimer...). Something that might help indexing the DB file content: All items are added to the items table with ever-growing item id, so it is pretty easy extracting all new items when saving the max item id from the last crawl. I have to say that it is more problematic to find out what old items were dropped. There is no easy way to determine it from a DB snapshot. I don't know about cooperative Beagle usage. If there is an easy way to interface with Beagle and to tell it about new/deleted items/feeds (maybe loosely couple like DBUS) it might be worth adding such functionality to Liferea. But please note that I do not drive any activities in this direction."
*** Bug 544061 has been marked as a duplicate of this bug. ***
*** Bug 564975 has been marked as a duplicate of this bug. ***
so the defunct liferea backend is still around in beagle 0.3.9, and the liferea maintainer has labelled my bug report "invalid", indicating that he has no intention to fix it. Wouldn't it be the best to drop the useless liferea backend by now, to avoid confusion?
I agree... I think we should disable the liferea backend in the forthcoming releases.
Beagle is not under active development anymore and had its last code changes in early 2011. Its codebase has been archived (see bug 796735): https://gitlab.gnome.org/Archive/beagle/commits/master "tracker" is an available alternative. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.