Bug#837177: icedove: the feed url could not be found

2016-12-04 Thread Carsten Schoenert
Hello Jens, On Sat, Dec 03, 2016 at 04:07:02PM +0100, Jens Reyer wrote: > Thunderbird 52.0 ESR will be released 2017-03-07. If I understood the > release model correctly, 52.2 ESR will be the first version of this > series that will be uploaded to stretch. It will be released on 2017-06-13. > >

Bug#837177: icedove: the feed url could not be found

2016-12-03 Thread Jens Reyer
control: tags -1 + patch Hi Carsten On 25.10.2016 07:28, Carsten Schoenert wrote: > On Mon, Oct 24, 2016 at 10:22:58PM +0200, Jens Reyer wrote: >> The changes have been committed upstream by now (Target Milestone: >> Thunderbird 52.0). > > thanks for figuring out and adding additional

Bug#837177: icedove: the feed url could not be found

2016-10-24 Thread Carsten Schoenert
Hello Jens, On Mon, Oct 24, 2016 at 10:22:58PM +0200, Jens Reyer wrote: > Hi again, > > I again had issues subscribing to a feed getting only the meaningless > error message "The Feed URL could not be found. Please check the name > and try again". > > So I tested a new version of the patches

Bug#837177: icedove: the feed url could not be found

2016-10-24 Thread Jens Reyer
control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=497488 control: tags -1 + fixed-upstream Hi again, I again had issues subscribing to a feed getting only the meaningless error message "The Feed URL could not be found. Please check the name and try again". So I tested a new

Bug#837177: icedove: the feed url could not be found

2016-10-04 Thread Jens Reyer
Followup-For: Bug #837177 Control: tags -1 - newcomer [ Removing the tag newcomer which is meant for easy bugs with a known solution, see https://www.debian.org/Bugs/Developer#tags ] Summary: I could reproduce this, but since yesterday it's working again *without* updating icedove itself.

Bug#837177: icedove: the feed url could not be found

2016-09-09 Thread mudongliang
Package: icedove Version: 1:45.2.0-4+b1 Severity: normal Tags: newcomer Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What