Bug#433393: liferea doesn't update any feeds after migration to new format
On 17/03/2008, Luis Rodrigo Gallardo Cruz [EMAIL PROTECTED] wrote: On Mon, Mar 17, 2008 at 02:21:14PM +0200, Eddy Petrișor wrote: Luis Rodrigo Gallardo Cruz wrote: On Thu, Mar 13, 2008 at 02:33:54AM +0200, Eddy Petrișor wrote: On to more promising lands: Could you try running with --debug-update, please? I moved away the ~/.liferea_1.4 directory (safe copy) and ran: liferea --debug-update 21 | tee liferea_update The log is attached. I hate Heisenbugs. Not sure this is one. I see nothing obviously wrong in this log. Even worse, there are entries there about updating the feeds, mentioning relatively recent entries in, for example, Debian Planet. Did it keep failing after this update? Yes, for instance, Debian Planet is still stuck at that post, Sami Haahtinen: Installing Debian on NSLU2 from the 6th of March. Mmm. This makes me think it's reading them but then not commiting them to the database. Maybe something in the cache settings is malfunctioning. Do you want me to send also the .liferea dir on which the upgrade is based? Yes, please, unless it contains private data. Nothing that isn't already on the net :-) Will do so when I get home. Please ping me again if I don't send anything within 24 hours. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein
Bug#433393: liferea doesn't update any feeds after migration to new format
Lars Lindner wrote: On Mon, Mar 17, 2008 at 7:53 PM, Eddy Petrișor [EMAIL PROTECTED] wrote: Lars Lindner wrote: To be honest your error report is pretty vague and one cannot really determine what you problem is. You really need to provide more details! For example I'm not sure you told how you trigger updates? I find this rather offensive, since I tried my best to provide all the required info until now. And, by the way, I already said how I trigger updates[1]. Also, when starting the application, the updates are automatically triggered. I didn't really read the original reference. And I do admit being impolite. No problem. Nonetheless I identified the problem. You do massively mark posts as important (flagged). Which is not forbidden, but was totally unexpected by me when I implemented the merging algorithm. Heh :-) . I usually do that so I can come back to them at any time I want to do read about the subject of the post. Is a way of archiving for me (since I saw is he only way to make liferea keep those posts from being lost into nothingness). Flagged items do have the property of never being dropped from Which is good :-), from my PoV. cache, but at the same moment we have a cache limit that the merging algorithm has to cope with. And the current calculation is simple: if the cache limit is 100 (like in your case and per default) and there are 100 (or more) flagged items that must never be dropped, then there is just no room to add new items. kaboom :-) As a temporary workaround you should increase the cache limit for all affected feeds (like the Debian Planet feed). I have, but it seems it already lost some of the items of the day... I'll probably change the limit first, then upgrade once more to the new format ;-) . For a real solution I need to think of something like having a soft cache limit that might be extended to # flagged items + # items in downloaded feed That is probably what would work for my case. Arghh... I don't like changing the merging mechanism... Tough luck :-) . But I appreciate this, and kudos for liferea. (BTW, I'll probably send another BR about it disrupting with my desire to have low battery consumption since it does polling and wakes up the CPU rather often.) -- Regards, EddyP = Imagination is more important than knowledge A.Einstein
Bug#433393: liferea doesn't update any feeds after migration to new format
Luis Rodrigo Gallardo Cruz wrote: On Mon, Mar 17, 2008 at 09:48:40PM +0200, Eddy Petrișor wrote: Lars Lindner wrote: Nonetheless I identified the problem. You do massively mark posts as important (flagged). Which is not forbidden, but was totally unexpected by me when I implemented the merging algorithm. Heh :-) . I usually do that so I can come back to them at any time I want to do read about the subject of the post. Is a way of archiving for me (since I saw is he only way to make liferea keep those posts from being lost into nothingness). Flagged items do have the property of never being dropped from Which is good :-), from my PoV. cache, but at the same moment we have a cache limit that the merging algorithm has to cope with. And the current calculation is simple: if the cache limit is 100 (like in your case and per default) and there are 100 (or more) flagged items that must never be dropped, then there is just no room to add new items. kaboom :-) As a temporary workaround you should increase the cache limit for all affected feeds (like the Debian Planet feed). I have, but it seems it already lost some of the items of the day... I'll probably change the limit first, then upgrade once more to the new format ;-) . If this works for you, please let me know. I'll then downgrade this report's severity but leave it open as a hint for others. Yes, it does, but why hide/bury it? Probably Lars will provide a fix soon and the problem will still be visible on an Etch-Lenny upgrade, if missed. I'd say there isn't a need for a severity downgrade, especially since the bug looks like is unreproducible at a first glance. (BTW, I'll probably send another BR about it disrupting with my desire to have low battery consumption since it does polling and wakes up the CPU rather often.) Does it? We had a round of updates back in 1.2 dealing with this. According to powertop we got down to a rather acceptable level, IIRC. I will look into this. I was surely talking about the previous version I had installed which was pre 1.2. But since the updates issue prevented me from using liferea, it also prevented me from observing if this is still true. Will look into it. Please interpret no answer/new BR as a confirmation of your words ;-) . -- Regards, EddyP = Imagination is more important than knowledge A.Einstein
Bug#433393: liferea doesn't update any feeds after migration to new format
Lars Lindner wrote: On Mon, Mar 17, 2008 at 9:37 PM, Eddy Petrișor [EMAIL PROTECTED] wrote: Luis Rodrigo Gallardo Cruz wrote: If this works for you, please let me know. I'll then downgrade this report's severity but leave it open as a hint for others. Yes, it does, but why hide/bury it? Probably Lars will provide a fix soon and the problem will still be visible on an Etch-Lenny upgrade, if missed. I'd say there isn't a need for a severity downgrade, especially since the bug looks like is unreproducible at a first glance. I fixed this in SVN with this revision: http://liferea.svn.sourceforge.net/viewvc/liferea?view=revrevision=3766 Solution will be released upstream around next weekend with 1.4.15. I've tested the change for effectiveness with the cache files you provided some mails ago. I'll monitor it for stability some more days... But I think the change is not very intrusive, so it propably will be ok. Kewl! :-) Thanks Lars! -- Regards, EddyP = Imagination is more important than knowledge A.Einstein
Bug#433393: liferea doesn't update any feeds after migration to new format
On Mon, Mar 17, 2008 at 02:21:14PM +0200, Eddy Petrișor wrote: Luis Rodrigo Gallardo Cruz wrote: On Thu, Mar 13, 2008 at 02:33:54AM +0200, Eddy Petrișor wrote: On to more promising lands: Could you try running with --debug-update, please? I moved away the ~/.liferea_1.4 directory (safe copy) and ran: liferea --debug-update 21 | tee liferea_update The log is attached. I hate Heisenbugs. Not sure this is one. I see nothing obviously wrong in this log. Even worse, there are entries there about updating the feeds, mentioning relatively recent entries in, for example, Debian Planet. Did it keep failing after this update? Yes, for instance, Debian Planet is still stuck at that post, Sami Haahtinen: Installing Debian on NSLU2 from the 6th of March. Mmm. This makes me think it's reading them but then not commiting them to the database. Maybe something in the cache settings is malfunctioning. Do you want me to send also the .liferea dir on which the upgrade is based? Yes, please, unless it contains private data. Note that the message after the update refers to an inexistent ~/.liferea_1.2 directory. You might want to fix that, too. Should I open another bug about this? Yes, please. Still, could it be because the upgrade is not made through an intermediate 1.2 version? I don't think so. I tried updating a default 1.0 install directly to 1.4 and it all worked without fault. So the whole thing has probably something to do with your data. signature.asc Description: Digital signature
Bug#433393: liferea doesn't update any feeds after migration to new format
On Mon, Mar 17, 2008 at 4:33 PM, Luis Rodrigo Gallardo Cruz [EMAIL PROTECTED] wrote: On Mon, Mar 17, 2008 at 02:21:14PM +0200, Eddy Petrișor wrote: Luis Rodrigo Gallardo Cruz wrote: On Thu, Mar 13, 2008 at 02:33:54AM +0200, Eddy Petrișor wrote: On to more promising lands: Could you try running with --debug-update, please? I moved away the ~/.liferea_1.4 directory (safe copy) and ran: liferea --debug-update 21 | tee liferea_update The log is attached. I hate Heisenbugs. Not sure this is one. I see nothing obviously wrong in this log. Even worse, there are entries there about updating the feeds, mentioning relatively recent entries in, for example, Debian Planet. Did it keep failing after this update? Yes, for instance, Debian Planet is still stuck at that post, Sami Haahtinen: Installing Debian on NSLU2 from the 6th of March. Mmm. This makes me think it's reading them but then not commiting them to the database. Maybe something in the cache settings is malfunctioning. I can think of several scenarios you could be in: 1.) No updates saved to disk 2.) No updates executed at all 3.) No updates results processed 4.) No network connection. In case of 1.) you should see DB error messages on the command line. To verify this please run at least once on the command line and check for suspicious output. You might also run once with command line option --debug-db and check for errors. In case of 2.) you can check using the Update Monitor options in the Tools menu. This will open a dialog presenting a list of all subscriptions that are to be updated and all that are downloaded right now. Here you should check wether there are feeds in the queue at all and if those are processed after a while. In case of 3.) you should check the output of a run with command line option --debug-update for HTTP error codes. In case of 4.) please check if the online/offline icon in the lower left corner displays the online icon. Also you should check the icons in the feed list wether they symbolize an unreachable state (by being replaced with error symbols). In general you should check what the status bar says when you perform an update (of either single feeds or all feeds). To be honest your error report is pretty vague and one cannot really determine what you problem is. You really need to provide more details! For example I'm not sure you told how you trigger updates? Regards, Lars
Bug#433393: liferea doesn't update any feeds after migration to new format
On Mon, Mar 17, 2008 at 9:37 PM, Eddy Petrișor [EMAIL PROTECTED] wrote: Luis Rodrigo Gallardo Cruz wrote: On Mon, Mar 17, 2008 at 09:48:40PM +0200, Eddy Petrișor wrote: Lars Lindner wrote: Nonetheless I identified the problem. You do massively mark posts as important (flagged). Which is not forbidden, but was totally unexpected by me when I implemented the merging algorithm. Heh :-) . I usually do that so I can come back to them at any time I want to do read about the subject of the post. Is a way of archiving for me (since I saw is he only way to make liferea keep those posts from being lost into nothingness). Flagged items do have the property of never being dropped from Which is good :-), from my PoV. cache, but at the same moment we have a cache limit that the merging algorithm has to cope with. And the current calculation is simple: if the cache limit is 100 (like in your case and per default) and there are 100 (or more) flagged items that must never be dropped, then there is just no room to add new items. kaboom :-) As a temporary workaround you should increase the cache limit for all affected feeds (like the Debian Planet feed). I have, but it seems it already lost some of the items of the day... I'll probably change the limit first, then upgrade once more to the new format ;-) . If this works for you, please let me know. I'll then downgrade this report's severity but leave it open as a hint for others. Yes, it does, but why hide/bury it? Probably Lars will provide a fix soon and the problem will still be visible on an Etch-Lenny upgrade, if missed. I'd say there isn't a need for a severity downgrade, especially since the bug looks like is unreproducible at a first glance. I fixed this in SVN with this revision: http://liferea.svn.sourceforge.net/viewvc/liferea?view=revrevision=3766 Solution will be released upstream around next weekend with 1.4.15. I've tested the change for effectiveness with the cache files you provided some mails ago. I'll monitor it for stability some more days... But I think the change is not very intrusive, so it propably will be ok. Regards, Lars
Bug#433393: liferea doesn't update any feeds after migration to new format
On Mon, Mar 17, 2008 at 7:53 PM, Eddy Petrișor [EMAIL PROTECTED] wrote: Lars Lindner wrote: On Mon, Mar 17, 2008 at 4:33 PM, Luis Rodrigo Gallardo Cruz [EMAIL PROTECTED] wrote: On Mon, Mar 17, 2008 at 02:21:14PM +0200, Eddy Petrișor wrote: Luis Rodrigo Gallardo Cruz wrote: On Thu, Mar 13, 2008 at 02:33:54AM +0200, Eddy Petrișor wrote: On to more promising lands: Could you try running with --debug-update, please? I moved away the ~/.liferea_1.4 directory (safe copy) and ran: liferea --debug-update 21 | tee liferea_update The log is attached. I hate Heisenbugs. Not sure this is one. I see nothing obviously wrong in this log. Even worse, there are entries there about updating the feeds, mentioning relatively recent entries in, for example, Debian Planet. Did it keep failing after this update? Yes, for instance, Debian Planet is still stuck at that post, Sami Haahtinen: Installing Debian on NSLU2 from the 6th of March. Mmm. This makes me think it's reading them but then not commiting them to the database. Maybe something in the cache settings is malfunctioning. I can think of several scenarios you could be in: 1.) No updates saved to disk 2.) No updates executed at all 3.) No updates results processed 4.) No network connection. In case of 1.) you should see DB error messages on the command line. To verify this please run at least once on the command line and check for suspicious output. You might also run once with command line option --debug-db and check for errors. log attached, my untrained eye didn't spot any of those. In case of 2.) you can check using the Update Monitor options in the Tools menu. This will open a dialog presenting a list of all subscriptions that are to be updated and all that are downloaded right now. Here you should check wether there are feeds in the queue at all and if those are processed after a while. They are executed. I checked the Update Monitor and all the expected (I focused on Planet Debian) feeds appear and are processed rather quickly(didn't have to wait more than a few seconds) in front of my eyes. In case of 3.) you should check the output of a run with command line option --debug-update for HTTP error codes. The log for update is also attached (liferea-debug-upd.log) I won't pretend I know the http protocol enough to know what I'm talking about, but this looks odd: UPDATE: trying to merge Planet Debian to node id ymxftff UPDATE: - not adding Planet Debian to node id ymxftff... UPDATE: trying to merge Planet Debian to node id ymxftff UPDATE: - not adding Planet Debian to node id ymxftff... UPDATE: trying to merge The Linux Gang - Daily Top Blog Posts on Linux - Powered by SocialRank to node id ym xftff UPDATE: - not adding The Linux Gang - Daily Top Blog Posts on Linux - Powered by SocialRank to node id ymxf tff... UPDATE: trying to merge The Linux Gang - Daily Top Blog Posts on Linux - Powered by SocialRank to node id ym xftff UPDATE: - not adding The Linux Gang - Daily Top Blog Posts on Linux - Powered by SocialRank to node id ymxf tff... [...] This is also odd (why does it say the content didn't change?) UPDATE: trying to merge Planet Debian to node id ymxftff UPDATE: - not adding Planet Debian to node id ymxftff... UPDATE: 0 new items, cache limit is 100 - dropping 0 items UPDATE: merge itemset took 0,011s UPDATE: download result - HTTP status: 304, error: 1, netio error:0, data: 0 UPDATE: request (http:) finished UPDATE: processing request (http://www.debian.org/News/weekly/dwn.en.rdf) UPDATE: downloading http://www.debian.org/News/weekly/dwn.en.rdf UPDATE: download result - HTTP status: 200, error: 0, netio error:0, data: 19272560 UPDATE: request (http:) finished UPDATE: processing request (http://planet.debian.org/rss20.xml) UPDATE: downloading http://planet.debian.org/rss20.xml UPDATE: discovered feed format: rss UPDATE: old item set 0x2c282da0 of (node id=slgapfb): UPDATE: trying to merge Package Build Status to node id slgapfb UPDATE: - not adding Package Build Status to node id slgapfb... In case of 4.) please check if the online/offline icon in the lower left corner displays the online icon. Also you should check the icons in the feed list wether they symbolize an unreachable state (by being replaced with error symbols). Is online. All the feeds wear their individual logos. In general you should check what the status bar says when you perform an update (of either single feeds or all feeds). The status bar says explicitly Is updating the feeds, one by one, but also says that nothing changed. To be honest your error report is pretty vague and one cannot really determine what you problem is. You really need to
Bug#433393: liferea doesn't update any feeds after migration to new format
On Mon, Mar 17, 2008 at 09:48:40PM +0200, Eddy Petrișor wrote: Lars Lindner wrote: Nonetheless I identified the problem. You do massively mark posts as important (flagged). Which is not forbidden, but was totally unexpected by me when I implemented the merging algorithm. Heh :-) . I usually do that so I can come back to them at any time I want to do read about the subject of the post. Is a way of archiving for me (since I saw is he only way to make liferea keep those posts from being lost into nothingness). Flagged items do have the property of never being dropped from Which is good :-), from my PoV. cache, but at the same moment we have a cache limit that the merging algorithm has to cope with. And the current calculation is simple: if the cache limit is 100 (like in your case and per default) and there are 100 (or more) flagged items that must never be dropped, then there is just no room to add new items. kaboom :-) As a temporary workaround you should increase the cache limit for all affected feeds (like the Debian Planet feed). I have, but it seems it already lost some of the items of the day... I'll probably change the limit first, then upgrade once more to the new format ;-) . If this works for you, please let me know. I'll then downgrade this report's severity but leave it open as a hint for others. (BTW, I'll probably send another BR about it disrupting with my desire to have low battery consumption since it does polling and wakes up the CPU rather often.) Does it? We had a round of updates back in 1.2 dealing with this. According to powertop we got down to a rather acceptable level, IIRC. signature.asc Description: Digital signature
Bug#433393: liferea doesn't update any feeds after migration to new format
Luis Rodrigo Gallardo Cruz wrote:
On Thu, Mar 13, 2008 at 02:33:54AM +0200, Eddy Petrișor wrote:
Luis Rodrigo Gallardo Cruz wrote:
And the migration of *that* is done by a simple copying over of the
file to the new .liferea_1.4 dir. Which pretty much rules out an error
there. Still, just to make sure, please take a look at that file and
try to see the entries for the failing feeds and compare them with the
file in the new dir.
0 [EMAIL PROTECTED] ~ $ grep -n 'updateInterval' ~/.liferea/feedlist.opml | sed
-r -e 's#^.*(text=[^]*).*(updateInterval=[^]*).*$#\1 \2#g'
/tmp/strippeduiold
0 [EMAIL PROTECTED] ~ $ grep -n 'updateInterval' ~/.liferea_1.4/feedlist.opml |
sed -r -e 's#^.*(text=[^]*).*(updateInterval=[^]*).*$#\1 \2#g'
/tmp/strippeduinew
0 [EMAIL PROTECTED] ~ $ diff -u /tmp/strippedui{old,new}
--- /tmp/strippeduiold 2008-03-13 01:35:38.0 +0200
+++ /tmp/strippeduinew 2008-03-13 01:35:48.0 +0200
@@ -17,7 +17,7 @@
text=Heron's Perch updateInterval=-1
text=Schneier on Security updateInterval=-1
text=Joel on Software updateInterval=-1
-text=mariuss' weblog - updateInterval=-1
+text=mariuss' weblog - updateInterval=-1
text=Planet Haskell updateInterval=-1
text=Stevey's Blog Rants updateInterval=-1
text=Razvan Patrascioiu - public_html updateInterval=-1
@@ -28,9 +28,6 @@
text=Programming updateInterval=-1
text=Real World Haskell: recent comments updateInterval=-1
text=Natali Del Conte updateInterval=-1
-text=Unread updateInterval=-2
-text=Flagged updateInterval=-2
text=ATI Proprietary Linux Driver Releases updateInterval=360
text=Syllable.org updateInterval=-1
-text=svn-buildpackage updateInterval=-2
text=Latest Secunia Security Advisories updateInterval=30
Nothing wrong here, it seems.
On to more promising lands:
Could you try running with --debug-update, please?
I moved away the ~/.liferea_1.4 directory (safe copy) and ran:
liferea --debug-update 21 | tee liferea_update
The log is attached.
I hate Heisenbugs.
Not sure this is one.
I see nothing obviously wrong in this log. Even worse, there are
entries there about updating the feeds, mentioning relatively recent
entries in, for example, Debian Planet.
Did it keep failing after this update?
Yes, for instance, Debian Planet is still stuck at that post, Sami Haahtinen: Installing Debian on
NSLU2 from the 6th of March.
Do you want me to send also the .liferea dir on which the upgrade is based?
Note that the message after the update refers to an inexistent
~/.liferea_1.2 directory. You might want to fix that, too. Should I open
another bug about this?
Yes, please.
Still, could it be because the upgrade is not made through an intermediate 1.2
version?
--
Regards,
EddyP
=
Imagination is more important than knowledge A.Einstein
Bug#433393: liferea doesn't update any feeds after migration to new format
On Thu, Mar 13, 2008 at 02:33:54AM +0200, Eddy Petrișor wrote:
Luis Rodrigo Gallardo Cruz wrote:
And the migration of *that* is done by a simple copying over of the
file to the new .liferea_1.4 dir. Which pretty much rules out an error
there. Still, just to make sure, please take a look at that file and
try to see the entries for the failing feeds and compare them with the
file in the new dir.
0 [EMAIL PROTECTED] ~ $ grep -n 'updateInterval' ~/.liferea/feedlist.opml |
sed
-r -e 's#^.*(text=[^]*).*(updateInterval=[^]*).*$#\1 \2#g'
/tmp/strippeduiold
0 [EMAIL PROTECTED] ~ $ grep -n 'updateInterval' ~/.liferea_1.4/feedlist.opml
|
sed -r -e 's#^.*(text=[^]*).*(updateInterval=[^]*).*$#\1 \2#g'
/tmp/strippeduinew
0 [EMAIL PROTECTED] ~ $ diff -u /tmp/strippedui{old,new}
--- /tmp/strippeduiold2008-03-13 01:35:38.0 +0200
+++ /tmp/strippeduinew2008-03-13 01:35:48.0 +0200
@@ -17,7 +17,7 @@
text=Heron's Perch updateInterval=-1
text=Schneier on Security updateInterval=-1
text=Joel on Software updateInterval=-1
-text=mariuss' weblog - updateInterval=-1
+text=mariuss' weblog - updateInterval=-1
text=Planet Haskell updateInterval=-1
text=Stevey's Blog Rants updateInterval=-1
text=Razvan Patrascioiu - public_html updateInterval=-1
@@ -28,9 +28,6 @@
text=Programming updateInterval=-1
text=Real World Haskell: recent comments updateInterval=-1
text=Natali Del Conte updateInterval=-1
-text=Unread updateInterval=-2
-text=Flagged updateInterval=-2
text=ATI Proprietary Linux Driver Releases updateInterval=360
text=Syllable.org updateInterval=-1
-text=svn-buildpackage updateInterval=-2
text=Latest Secunia Security Advisories updateInterval=30
Nothing wrong here, it seems.
On to more promising lands:
Could you try running with --debug-update, please?
I moved away the ~/.liferea_1.4 directory (safe copy) and ran:
liferea --debug-update 21 | tee liferea_update
The log is attached.
I hate Heisenbugs.
I see nothing obviously wrong in this log. Even worse, there are
entries there about updating the feeds, mentioning relatively recent
entries in, for example, Debian Planet.
Did it keep failing after this update?
Note that the message after the update refers to an inexistent
~/.liferea_1.2 directory. You might want to fix that, too. Should I open
another bug about this?
Yes, please.
signature.asc
Description: Digital signature
Bug#433393: liferea doesn't update any feeds after migration to new format
Luis Rodrigo Gallardo Cruz wrote:
On Wed, Mar 12, 2008 at 12:34:47AM +0200, Eddy Petrișor wrote:
On 11/03/2008, Luis Rodrigo Gallardo Cruz [EMAIL PROTECTED] wrote:
On Tue, Mar 11, 2008 at 01:07:04AM +0200, Eddy Petrișor wrote:
Luis Rodrigo Gallardo Cruz wrote:
Otherwise, please check the feed properties to see if the update
intervals were imported correctly. Check also the default interval set
in preferences.
I don't care about each feed's update interval, I override all with the
default interval which is 15 minutes.
But, did liferea import that setting correctly from the previous version?
REPLY=have to check and need help to see the old setting
[ $that ==$deafult_update_interval ] REPLY=yes
(grumble grumble)
I've taken a look at a migration from 1.0. The update interval setting
is stored in an attribute of the feed entry in ~/.liferea/feedlist.opml
And the migration of *that* is done by a simple copying over of the
file to the new .liferea_1.4 dir. Which pretty much rules out an error
there. Still, just to make sure, please take a look at that file and
try to see the entries for the failing feeds and compare them with the
file in the new dir.
0 [EMAIL PROTECTED] ~ $ grep -n 'updateInterval' ~/.liferea/feedlist.opml | sed -r -e
's#^.*(text=[^]*).*(updateInterval=[^]*).*$#\1 \2#g' /tmp/strippeduiold
0 [EMAIL PROTECTED] ~ $ grep -n 'updateInterval' ~/.liferea_1.4/feedlist.opml | sed -r -e
's#^.*(text=[^]*).*(updateInterval=[^]*).*$#\1 \2#g' /tmp/strippeduinew
0 [EMAIL PROTECTED] ~ $ diff -u /tmp/strippedui{old,new}
--- /tmp/strippeduiold 2008-03-13 01:35:38.0 +0200
+++ /tmp/strippeduinew 2008-03-13 01:35:48.0 +0200
@@ -17,7 +17,7 @@
text=Heron's Perch updateInterval=-1
text=Schneier on Security updateInterval=-1
text=Joel on Software updateInterval=-1
-text=mariuss' weblog - updateInterval=-1
+text=mariuss' weblog - updateInterval=-1
text=Planet Haskell updateInterval=-1
text=Stevey's Blog Rants updateInterval=-1
text=Razvan Patrascioiu - public_html updateInterval=-1
@@ -28,9 +28,6 @@
text=Programming updateInterval=-1
text=Real World Haskell: recent comments updateInterval=-1
text=Natali Del Conte updateInterval=-1
-text=Unread updateInterval=-2
-text=Flagged updateInterval=-2
text=ATI Proprietary Linux Driver Releases updateInterval=360
text=Syllable.org updateInterval=-1
-text=svn-buildpackage updateInterval=-2
text=Latest Secunia Security Advisories updateInterval=30
On to more promising lands:
Could you try running with --debug-update, please?
I moved away the ~/.liferea_1.4 directory (safe copy) and ran:
liferea --debug-update 21 | tee liferea_update
The log is attached.
Note that the message after the update refers to an inexistent ~/.liferea_1.2 directory. You might
want to fix that, too. Should I open another bug about this?
--
Regards,
EddyP
=
Imagination is more important than knowledge A.Einstein
liferea_update.bz2
Description: application/bzip
Bug#433393: liferea doesn't update any feeds after migration to new format
On Tue, Mar 11, 2008 at 01:07:04AM +0200, Eddy Petrișor wrote: Luis Rodrigo Gallardo Cruz wrote: Otherwise, please check the feed properties to see if the update intervals were imported correctly. Check also the default interval set in preferences. I don't care about each feed's update interval, I override all with the default interval which is 15 minutes. But, did liferea import that setting correctly from the previous version? signature.asc Description: Digital signature
Bug#433393: liferea doesn't update any feeds after migration to new format
On 11/03/2008, Luis Rodrigo Gallardo Cruz [EMAIL PROTECTED] wrote: On Tue, Mar 11, 2008 at 01:07:04AM +0200, Eddy Petrișor wrote: Luis Rodrigo Gallardo Cruz wrote: Otherwise, please check the feed properties to see if the update intervals were imported correctly. Check also the default interval set in preferences. I don't care about each feed's update interval, I override all with the default interval which is 15 minutes. But, did liferea import that setting correctly from the previous version? REPLY=have to check and need help to see the old setting [ $that ==$deafult_update_interval ] REPLY=yes -- Regards, EddyP = Imagination is more important than knowledge A.Einstein
Bug#433393: liferea doesn't update any feeds after migration to new format
On Wed, Mar 12, 2008 at 12:34:47AM +0200, Eddy Petrișor wrote: On 11/03/2008, Luis Rodrigo Gallardo Cruz [EMAIL PROTECTED] wrote: On Tue, Mar 11, 2008 at 01:07:04AM +0200, Eddy Petrișor wrote: Luis Rodrigo Gallardo Cruz wrote: Otherwise, please check the feed properties to see if the update intervals were imported correctly. Check also the default interval set in preferences. I don't care about each feed's update interval, I override all with the default interval which is 15 minutes. But, did liferea import that setting correctly from the previous version? REPLY=have to check and need help to see the old setting [ $that ==$deafult_update_interval ] REPLY=yes (grumble grumble) I've taken a look at a migration from 1.0. The update interval setting is stored in an attribute of the feed entry in ~/.liferea/feedlist.opml And the migration of *that* is done by a simple copying over of the file to the new .liferea_1.4 dir. Which pretty much rules out an error there. Still, just to make sure, please take a look at that file and try to see the entries for the failing feeds and compare them with the file in the new dir. On to more promising lands: Could you try running with --debug-update, please? signature.asc Description: Digital signature
Bug#433393: liferea doesn't update any feeds after migration to new format
Luis Rodrigo Gallardo Cruz wrote: On Fri, Mar 07, 2008 at 08:05:45PM +0200, Eddy Petrișor wrote: Since liferea I updated to this version and liferea updated its database to the new format, none of the feeds are updated anymore. For instance, Planet Debian has the tip stuck on http://ressukka.net/blog/posts/20070517_debian_on_nslu2/ It seems either the upgrade or the database format upgrade, it has stuck. Does liferea start up correctly after the update? Yes, some of the feeds are updated, but not all. If not, maybe you hit #469245, please try the workaround suggested there (delete ~/.liferea_1.4/new_subscription and restart liferea). Otherwise, please check the feed properties to see if the update intervals were imported correctly. Check also the default interval set in preferences. I don't care about each feed's update interval, I override all with the default interval which is 15 minutes. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein
Bug#433393: liferea doesn't update any feeds after migration to new format
retitle 433393 liferea doesn't update some feeds after migration to new format thanks Eddy Petrișor wrote: Luis Rodrigo Gallardo Cruz wrote: On Fri, Mar 07, 2008 at 08:05:45PM +0200, Eddy Petrișor wrote: Since liferea I updated to this version and liferea updated its database to the new format, none of the feeds are updated anymore. For instance, Planet Debian has the tip stuck on http://ressukka.net/blog/posts/20070517_debian_on_nslu2/ It seems either the upgrade or the database format upgrade, it has stuck. Does liferea start up correctly after the update? Yes, some of the feeds are updated, but not all. If not, maybe you hit #469245, please try the workaround suggested there (delete ~/.liferea_1.4/new_subscription and restart liferea). Otherwise, please check the feed properties to see if the update intervals were imported correctly. Check also the default interval set in preferences. I don't care about each feed's update interval, I override all with the default interval which is 15 minutes. Still, it seems that some of the feeds are updated, but most of them are not. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein
Bug#433393: liferea doesn't update any feeds after migration to new format
Package: liferea Version: 1.4.12-1 Justification: doesn't do its basic functionality # I hope this works severity 433393 serious thanks --- Please enter the report below this line. --- Since liferea I updated to this version and liferea updated its database to the new format, none of the feeds are updated anymore. For instance, Planet Debian has the tip stuck on http://ressukka.net/blog/posts/20070517_debian_on_nslu2/ It seems either the upgrade or the database format upgrade, it has stuck. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.24.2-bounty Debian Release: lenny/sid 900 testing security.debian.org 900 testing ftp.ro.debian.org 10 unstableftp.ro.debian.org --- Package information. --- Depends (Version) | Installed ==-+- gconf2 (= 2.10.1-2) | 2.20.1-3 libatk1.0-0(= 1.20.0) | 1.20.0-1 libc6 (= 2.7-1) | 2.7-6 libcairo2 (= 1.4.0) | 1.4.14-1 libdbus-glib-1-2 (= 0.74) | 0.74-1 libgcc1(= 1:4.1.1-21) | 1:4.3-20080202-1 libgconf2-4(= 2.13.5) | 2.20.1-3 libgcrypt11 (= 1.4.0) | 1.4.0-3 libglade2-0 (= 1:2.6.1) | 1:2.6.2-1 libglib2.0-0 (= 2.14.0) | 2.14.6-1 libgnutls26 (= 2.2.0-0) | 2.2.2-1 libgtk2.0-0(= 2.12.0) | 2.12.5-2 libice6 (= 1:1.0.0) | 2:1.0.4-1 liblua5.1-0| 5.1.3-1 libnm-glib0| 0.6.5-5 libnotify1 (= 0.4.4) | 0.4.4-3 libnotify1-gtk2.10 | libpango1.0-0 (= 1.18.4) | 1.18.4-1 libsm6 | 2:1.0.3-1+b1 libsqlite3-0(= 3.4.2) | 3.5.6-3 libstdc++6 (= 4.1.1-21) | 4.3-20080202-1 libx11-6 | 2:1.0.3-7 libxml2(= 2.6.27) | 2.6.31.dfsg-1 libxslt1.1 (= 1.1.18) | 1.1.22-1 libxul0d (= 1.8.1.4) | 1.8.1.12-2 zlib1g(= 1:1.1.4) | 1:1.2.3.3.dfsg-11 -- Regards, EddyP = Imagination is more important than knowledge A.Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433393: liferea doesn't update any feeds after migration to new format
On Fri, Mar 07, 2008 at 08:05:45PM +0200, Eddy Petrișor wrote: Since liferea I updated to this version and liferea updated its database to the new format, none of the feeds are updated anymore. For instance, Planet Debian has the tip stuck on http://ressukka.net/blog/posts/20070517_debian_on_nslu2/ It seems either the upgrade or the database format upgrade, it has stuck. Does liferea start up correctly after the update? If not, maybe you hit #469245, please try the workaround suggested there (delete ~/.liferea_1.4/new_subscription and restart liferea). Otherwise, please check the feed properties to see if the update intervals were imported correctly. Check also the default interval set in preferences. Thanks. signature.asc Description: Digital signature
