Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

Dang, you're right. It has only gone almost 9 months sometimes. Nice table. perl?

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

> Haha, what are you smoking? I don't even bother to look it up, I guess what I'm smoking are called "facts"? You said "Sometimes it goes more than a year between upstream's releases". This is false. The longest period ever between releases was 8.8 months, and the average time between

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

Haha, what are you smoking? I don't even bother to look it up, I guess there is not even dates in your changelog. It is more like 1-2 per calendar year maximum. The one that went into Debian's previous stable release and you made so much fuzz about, had been the last release for I don't know how

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

> Sometimes it goes more than a year between upstream's releases also, This has literally never happened. There are typically 4-8 releases a year, but there have never been fewer than 2 per year, since 1992.

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

Hi, With regards to the latest XScreenSaver release, which I hope will fix this issue, I was fast getting it packaged up in git, but it has sitting there for a while because I need to check all the Debian QA stuff, new policies, etc, and get someone to review it, but most importantly real life got

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

On Sat, 14 Oct 2017 17:37:26 -0700 Jamie Zawinski wrote: > Well, > > 5.36 was released on 11 Oct 2016, which, as of the date of this bug report, > was 1 year and 3 days old. > > 5.37, which contains webcollage updates, was released on 5 July 2017. > > The latency with which distros

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

Well, 5.36 was released on 11 Oct 2016, which, as of the date of this bug report, was 1 year and 3 days old. 5.37, which contains webcollage updates, was released on 5 July 2017. The latency with which distros package it up for you is entirely out of my hands.

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

On Fri, 13 Oct 2017 04:18:29 -0700 Jamie Zawinski wrote: > Here's an idea, try running a version of xscreensaver that is not over a year > old. > > Yes, you have made the mistake of using Debian. I realize that they go out of > their way to make that difficult for you. My

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

On Fri, 13 Oct 2017 04:18:29 -0700 Jamie Zawinski wrote: > Here's an idea, try running a version of xscreensaver that is not over a year > old. > > Yes, you have made the mistake of using Debian. I realize that they go out of > their way to make that difficult for you. My

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

Here's an idea, try running a version of xscreensaver that is not over a year old. Yes, you have made the mistake of using Debian. I realize that they go out of their way to make that difficult for you. My sympathies.

Bug#878373: xscreensaver-screensaver-webcollage: Fails to get resuls from google, bing, and instagram making collages repetitive.

Package: xscreensaver-screensaver-webcollage Version: 5.36-1 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I installed the screensaver and selected it, on running I observed