Bug#590147: Upgrade
severity 590147 important thanks On Sun, May 27, 2012 at 11:50:08AM +0200, Moritz Mühlenhoff wrote: On Mon, Nov 29, 2010 at 11:28:31AM +0200, Modestas Vainius wrote: The two are from my point of view RC No, the first part is not RC because: 1) it is rare enough 2) there is no data loss involved There is no info about the 2nd part and according to upstream, the bug has been there since etch (!!!) meaning two debian stable releases already have it. However, the debian bug has only been reported recently. This tells a lot about commodity of this bug. You may argue as much as you want but probability of this getting fixed is nearly 0% since it has not been fixed for many years and there is obvious lack of information. What is more, metakit has no future. Once akregrator is rewriten based on akonadi, this will go away. I propose to downgrade this to non-RC severity. If it all, it's a rare corner-case. Going ahead, since noone objected. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590147: Upgrade
On Mon, Nov 29, 2010 at 11:28:31AM +0200, Modestas Vainius wrote: The two are from my point of view RC No, the first part is not RC because: 1) it is rare enough 2) there is no data loss involved There is no info about the 2nd part and according to upstream, the bug has been there since etch (!!!) meaning two debian stable releases already have it. However, the debian bug has only been reported recently. This tells a lot about commodity of this bug. You may argue as much as you want but probability of this getting fixed is nearly 0% since it has not been fixed for many years and there is obvious lack of information. What is more, metakit has no future. Once akregrator is rewriten based on akonadi, this will go away. I propose to downgrade this to non-RC severity. If it all, it's a rare corner-case. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590147: Upgrade
On Mon, Nov 29, 2010 at 2:22 AM, Modestas Vainius modes...@vainius.eu wrote: tags 590147 help thanks Hello, On antradienis 09 Lapkritis 2010 11:23:53 Bastien ROUCARIES wrote: But now there are too many variables. To make things worse, akregator developement isn't very active upstream. I have not the skills to debug this bug, but they are some file that coul allow youy to reproduce it at http://bugs.kde.org/attachment.cgi?id=48011 All that stuff in bug report is useless because both this debian bug and upstream bug deal with consequences. When you see this crash and backtrace, the archive file had already been cut short and the data had already been lost. akregator is simply unable to read corrupt archive file on startup and rather than handling this condition gracefully, it crashes Do you agree that solving the first part of the problem will be really nice. Instead of alway crashing following a cosmics ray it will prompt and fix the error. . However, there is no information how and when akregator fails to write correct archive file or otherwise corrupts it. I agree also with this part. But it is a second bug Should I duplicate the bug ? The two are from my point of view RC So basically this bug is impossible to fix without a reliable way to reproduce it from the start to finish. During my 2 years of using akregator, I have never had this problem so there is not much I can do. Thanks -- Modestas Vainius modes...@vainius.eu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590147: Upgrade
Hello, On pirmadienis 29 Lapkritis 2010 10:21:13 Bastien ROUCARIES wrote: . However, there is no information how and when akregator fails to write correct archive file or otherwise corrupts it. I agree also with this part. But it is a second bug Should I duplicate the bug ? No. The two are from my point of view RC No, the first part is not RC because: 1) it is rare enough 2) there is no data loss involved There is no info about the 2nd part and according to upstream, the bug has been there since etch (!!!) meaning two debian stable releases already have it. However, the debian bug has only been reported recently. This tells a lot about commodity of this bug. You may argue as much as you want but probability of this getting fixed is nearly 0% since it has not been fixed for many years and there is obvious lack of information. What is more, metakit has no future. Once akregrator is rewriten based on akonadi, this will go away. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#590147: Upgrade
tags 590147 help thanks Hello, On antradienis 09 Lapkritis 2010 11:23:53 Bastien ROUCARIES wrote: But now there are too many variables. To make things worse, akregator developement isn't very active upstream. I have not the skills to debug this bug, but they are some file that coul allow youy to reproduce it at http://bugs.kde.org/attachment.cgi?id=48011 All that stuff in bug report is useless because both this debian bug and upstream bug deal with consequences. When you see this crash and backtrace, the archive file had already been cut short and the data had already been lost. akregator is simply unable to read corrupt archive file on startup and rather than handling this condition gracefully, it crashes. However, there is no information how and when akregator fails to write correct archive file or otherwise corrupts it. So basically this bug is impossible to fix without a reliable way to reproduce it from the start to finish. During my 2 years of using akregator, I have never had this problem so there is not much I can do. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Bug#590147: Upgrade
No this bug occurs after an upgrade. Upgrade from what version? upgrade to 1.6.5 I could start agregator after deleting all my archive... So crash each time or loss all archive. This supports my assumption that the problem is cache corruption. No it is an archive problem. Not a cahce problem. Cache could be purged (cahce does not have valuable data). Archive have valuable data and could not be purged without data loss It is for me release critical ask to kde teams but for me it is release critical. If I could reproduce it, I would agree it's RC. Why ? I loss my archive. Some are now closed blog that I like to read ? I loss my data = RC by default When cache is corrupte I could not start it again... I need toi manually remove archive or do some manual and boring workarround see http://bugs.kde.org/show_bug.cgi?id=116482#c205 But now there are too many variables. To make things worse, akregator developement isn't very active upstream. I have not the skills to debug this bug, but they are some file that coul allow youy to reproduce it at http://bugs.kde.org/attachment.cgi?id=48011 Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
