Debian Bug report logs - #819703
xscreensaver: please disable "This version of XScreenSaver is very old! Please upgrade!" message

Package: xscreensaver; Maintainer for xscreensaver is Tormod Volden <debian.tormod@gmail.com>; Source for xscreensaver is src:xscreensaver (PTS, buildd, popcon).

Reported by: Daniel Shahaf <danielsh@apache.org>

Date: Fri, 1 Apr 2016 03:03:01 UTC

Severity: important

Tags: patch

Merged with 820880

Found in versions xscreensaver/5.30-1, xscreensaver/5.30-1+deb8u1, xscreensaver/5.34-1

Fixed in versions xscreensaver/5.34-2, xscreensaver/5.30-1+deb8u2

Done: schwinn <al.schwinn@gsi.de>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to debian-bugs-dist@lists.debian.org, danielsh@apache.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Fri, 01 Apr 2016 03:03:05 GMT) (full text, mbox, link).

Acknowledgement sent to Daniel Shahaf <danielsh@apache.org>:
New Bug report received and forwarded. Copy sent to danielsh@apache.org, Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 03:03:05 GMT) (full text, mbox, link).

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Package: xscreensaver
Version: 5.34-1
Severity: normal
Tags: upstream patch

Dear Maintainer,

In the lock screen, XScreenSaver displays the following message in bold font:

    This version of XScreenSaver is very old! Please upgrade!

There is a similar warning when opening the "Screensaver" command from
the XFCE Applications Menu:

      _("Warning:\n\n"
        "This version of xscreensaver is VERY OLD!\n"
        "Please upgrade!\n"
        "\n"
        "http://www.jwz.org/xscreensaver/\n"
        "\n"
        "(If this is the latest version that your distro ships, then\n"
        "your distro is doing you a disservice. Build from source.)\n"
        ),

Please disable these warnings.

A proposed (untested) patch attached.

I know that the author has placed a Big Fat Warning in senescent_p()
asking distro maintainers not to remove those warnings.  However, as
a user I find these warnings rude and obnoxious, and I wish my computer
not to be obnoxious to me.  Therefore, I ask that you disable the
recency check, notwithstanding the author's request.

The author's wishes that users not bother him with bugs about old
versions of the software can surely be addressed without unavoidable
dialogs in *bold* or ALL CAPS presented _every time a user unlocks her
screensaver_, as well as every time a user tries to configure her
screensaver.  I can think of at least two ways off the top of my head¹,
that don't involve discrediting xscreensaver's downstreams or shouting
at users.

Thank you.

Daniel

¹ - include the release date, advice to upgrade, and a statement that
    upstream won't accept bug reports, all rendered in the typical running
    text font, wherever the version number is displayed; or
  - route users' bug reports to upstream through a web page that
    explains the issue; or
  - route users' bug reports to upstream through a web form that has
    a "Version number:" field and gives the "Out of date" error if the
    user filled in an old version number.

P.S. I'm reporting this against the version in stable/jessie, but as far
as I can tell, the problem still exists in git revision debian/5.33-1-4-gff0d1d4.

[patch.txt (text/x-diff, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Fri, 01 Apr 2016 04:33:03 GMT) (full text, mbox, link).

Acknowledgement sent to Jamie Zawinski <jwz@jwz.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 04:33:03 GMT) (full text, mbox, link).

Message #10 received at 819703@bugs.debian.org (full text, mbox, reply):

In the time it took me to read your whine, you could have upgraded your incredibly-out-of-date computer and saved us all the grief.

>  However, as a user I find these warnings rude and obnoxious, and I wish my computer not to be obnoxious to me. 

I find your request to be obnoxious and I wish to not have read it, but sadly we don't always get what we want.

--
Jamie Zawinski      https://www.jwz.org/      https://www.dnalounge.com/

Acknowledgement sent to Łukasz Stelmach <l.stelmach@samsung.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 07:54:04 GMT) (full text, mbox, link).

Message #15 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Dear Maintainer,

please update the xscreensaver package in both Jessie and Wheezy.

Thak you,
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[signature.asc (application/pgp-signature, inline)]

Acknowledgement sent to Axel Beckert <abe@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 07:57:06 GMT) (full text, mbox, link).

Message #20 received at 819703@bugs.debian.org (full text, mbox, reply):

Control: found -1 5.30-1

Hi,

Daniel Shahaf wrote:
> In the lock screen, XScreenSaver displays the following message in bold font:
> 
>     This version of XScreenSaver is very old! Please upgrade!

Indeed. Very annoying. Upstream obviously hasn't understood how
distributions work and what stable releases are.

> A proposed (untested) patch attached.

Tormod: Please fix this issue also in Debian Jessie via
jessie-proposed-updates where it probably annoys end users the most.

> I know that the author has placed a Big Fat Warning in senescent_p()
> asking distro maintainers not to remove those warnings.  However, as
> a user I find these warnings rude and obnoxious, and I wish my computer
> not to be obnoxious to me.  Therefore, I ask that you disable the
> recency check, notwithstanding the author's request.

I second this.

> The author's wishes that users not bother him with bugs about old
> versions of the software can surely be addressed without unavoidable
> dialogs in *bold* or ALL CAPS presented _every time a user unlocks her
> screensaver_, as well as every time a user tries to configure her
> screensaver.

That won't help. It will primarily help to scare people away from
software with stubborn upstream maintainers as it has happened in the
past with e.g. ion3 (stubborn license), micq (stating disagreement
between upstream and packager to users).

> ¹ - include the release date, advice to upgrade, and a statement that
>     upstream won't accept bug reports, all rendered in the typical running
>     text font, wherever the version number is displayed; or

I don't think "advice to upgrade" is much better than the current
situation, except that it doesn't involve CAPS-LOCK and exclamation
marks.

>   - route users' bug reports to upstream through a web page that
>     explains the issue; or
>   - route users' bug reports to upstream through a web form that has
>     a "Version number:" field and gives the "Out of date" error if the
>     user filled in an old version number.

That sounds like sane solutions for upstream. Nevertheless, that
doesn't solve our problem in Debian and its downstream distributions.

> P.S. I'm reporting this against the version in stable/jessie,

Sorry, you didn't. I've added the version (initially) in Jessie now.

> diff --git a/driver/prefs.c b/driver/prefs.c
> index 55bac7b..f9f96c3 100644
> --- a/driver/prefs.c
> +++ b/driver/prefs.c
> @@ -1663,6 +1663,8 @@ stop_the_insanity (saver_preferences *p)
>  Bool
>  senescent_p (void)
>  {
> +  return 0;
> +
>    /* If you are in here because you're planning on disabling this warning
>       before redistributing my software, please don't.

That doesn't fix the XFCE menu warning, too, right?

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Marked as found in versions xscreensaver/5.30-1. Request was from Axel Beckert <abe@debian.org> to 819703-submit@bugs.debian.org. (Fri, 01 Apr 2016 07:57:06 GMT) (full text, mbox, link).

Acknowledgement sent to Сергей Жлобо <sey@well-comm.ru>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 09:51:15 GMT) (full text, mbox, link).

Message #27 received at 819703@bugs.debian.org (full text, mbox, reply):

Hello, is it joke )?

Removed tag(s) upstream. Request was from Axel Beckert <beckert@phys.ethz.ch> to control@bugs.debian.org. (Fri, 01 Apr 2016 10:54:03 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Fri, 01 Apr 2016 11:06:07 GMT) (full text, mbox, link).

Acknowledgement sent to Roberto <roberto@zenvoid.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 11:06:07 GMT) (full text, mbox, link).

Message #34 received at 819703@bugs.debian.org (full text, mbox, reply):

It is not a joke, I've also noticed the message today, I was writing a
but report when I've noticed it was already reported. Since today
xscreensaver tells debian users that "your distro is doing you a
disservice. Build from source".

Acknowledgement sent to Richard Jasmin <frazzledjazz@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 11:54:16 GMT) (full text, mbox, link).

Message #39 received at 819703@bugs.debian.org (full text, mbox, reply):

Package: xscreensaver
Version: 5.30-1+deb8u1
Followup-For: Bug #819703

Dear Maintainer,

I have a better solution.
Dispense with the horse shit.

Either provide a upstream version to be packaged(and backported) or permanently
remove the offending code(and warnings).

and as per upstream:
needs to be backported or pushed into updates server. both may be options, but
when selected the updates are EXPECTED.
At least this update is NOT PRESENT.

Thats a packaging fault.
I know of QT5(core) and Mono (v4) updates missing also.
And debs are available, so dont gimmie that line.

Nobody asked for acenine response from ANY dev, and surely such is COMPLETELY
unwarranted. If you want your package included
in distributions, make the concessions necessary to maintain the codebase with
said.

Otherwise, either DONT OFFER the code, or DONT package it further.
Drop it from the repos if the maintainer wont comply.

That should be a debian core policy.
I know several here are also acenine (with reports) or are acenine C devs that
dont give a flying eff about anyone, but thats the wrong mentality to take
with anyone. More than half of the time said acenine devs have no clue what
they are coding.

Yes, I can put my code where my mouth is, despite my unpopular view on C.

Clearly bug reports and handling is yall policy, but being the nature of "whats
and whos" involved these reports should be taken more seriously
than frivious borsht.Its not about liking the bug reporter, its about dealing
with the bug. Maybe its not so serious, MAYBE ITS WORSE.
Clearly someone needs to get thier ass in gear.



-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xscreensaver depends on:
ii  libatk1.0-0          2.14.0-1
ii  libc6                2.19-18+deb8u3
ii  libcairo2            1.14.0-2.1
ii  libfontconfig1       2.11.0-6.3
ii  libfreetype6         2.5.2-3+deb8u1
ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u4
ii  libglade2-0          1:2.6.4-2
ii  libglib2.0-0         2.42.1-1
ii  libgtk2.0-0          2.24.25-3
ii  libice6              2:1.0.9-1+b1
ii  libpam0g             1.1.8-3.1+deb8u1
ii  libpango-1.0-0       1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-0    1.36.8-3
ii  libsm6               2:1.2.2-1+b1
ii  libx11-6             2:1.6.2-3
ii  libxext6             2:1.3.3-1
ii  libxi6               2:1.7.4-1+b2
ii  libxinerama1         2:1.1.3-1+b1
ii  libxml2              2.9.1+dfsg1-5+deb8u1
ii  libxmu6              2:1.1.2-1
ii  libxpm4              1:3.5.11-1+b1
ii  libxrandr2           2:1.4.2-1+b1
ii  libxrender1          1:0.9.8-1+b1
ii  libxt6               1:1.1.4-1+b1
ii  libxxf86vm1          1:1.1.3-1+b1
ii  xscreensaver-data    5.30-1+deb8u1

Versions of packages xscreensaver recommends:
ii  libjpeg-turbo-progs [libjpeg-progs]  1:1.3.1-12
ii  perl [perl5]                         5.20.2-3+deb8u4
ii  wamerican [wordlist]                 7.1-1

Versions of packages xscreensaver suggests:
ii  chromium [www-browser]      49.0.2623.108-1~deb8u1
ii  dillo [www-browser]         3.0.4-2+b1
ii  elinks [www-browser]        0.12~pre6-5+b2
ii  fortune-mod [fortune]       1:1.99.1-7
pn  gdm3 | kdm-gdmcompat        <none>
ii  iceweasel [www-browser]     38.7.1esr-1~deb8u1
ii  konqueror [www-browser]     4:4.14.2-1
ii  links2 [www-browser]        2.8-2+b3
ii  lynx-cur [www-browser]      2.8.9dev1-2+deb8u1
ii  opera-stable [www-browser]  36.0.2130.46
pn  qcam | streamer             <none>
ii  w3m [www-browser]           0.5.3-19
pn  xdaliclock                  <none>
pn  xfishtank                   <none>
ii  xscreensaver-gl             5.30-1+deb8u1

-- no debconf information

Acknowledgement sent to Sven Geggus <lists@fuchsschwanzdomain.de>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 12:27:06 GMT) (full text, mbox, link).

Message #44 received at 819703@bugs.debian.org (full text, mbox, reply):

Hello,

looking how I can try to avoid pissing off dozens of my users with this
message I have been looking at the code and came to the conclusion, that
this miss-feature will certainly also kill ReproducibleBuilds.

So bug 819595 might be related.

Regards

Sven

Message #49 received at 819703@bugs.debian.org (full text, mbox, reply):

Please ignore my last report. As the date in questions seems to be the date
of the last modification to the source code rather than a build date it will
not harm ReproducibleBuilds.

Sven

Acknowledgement sent to Santiago Vila <sanvila@unex.es>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 12:42:04 GMT) (full text, mbox, link).

Message #54 received at 819703@bugs.debian.org (full text, mbox, reply):

Hello.

At the risk of stating the obvious, I'm going to reply to this message
from the author, since it seems he reads the bugs reported to Debian.

On Thu, 31 Mar 2016, Jamie Zawinski wrote:

> In the time it took me to read your whine, you could have upgraded
> your incredibly-out-of-date computer and saved us all the grief.

Actually, that's not necessarily the case.

Packages in Debian stable only change when they have security bugs
(via security.debian.org), or (in certain cases) bugs of serious
severity, of the type that make them unsuitable for release.

Just "being old" is not a bug in itself, so it's not a reason good
enough to upgrade, or a reason to ask the user that he/she has
to upgrade.

Upgrading *all* the packages in Debian is quite easy: "apt-get upgrade".
You are absolutely right that it would take very little time to do
that, but not so right if you blidnly assume that a new package
somehow "has" to be available when doing "apt-get upgrade" when you
are using Debian stable.

Because stable is frozen and does not change except for security fixes
and very serious bugs.

Now, let's see what's wrong with old versions.

If you don't want to receive bugs about old versions, we understand
that completely. We don't like to receive bugs about old versions
either. The perfect bug submitter is the one that looks for the latest
version to confirm that it's not fixed yet.

To not bother upstream authors with reports about old versions, we
have our own bug tracking system. In theory, bugs about old versions
would never be forwarded to the author (via email, I mean).

> I find your request to be obnoxious and I wish to not have read it,
> but sadly we don't always get what we want.

If, as it seems, the author voluntarily subscribes to our bug tracking
system to receive all the bugs reported to Debian, that's fine
(in fact, the best upstream maintainers are the ones that do that).

But you can't then complain that you have to read bugs about old
version, that would be quite contradictory indeed.

Subscribing to a package or to a bug is like a mailing list, it's
either all or nothing.

If bugs about old version really bother you, you could just ignore
them. Nobody will ask you to fix something that it's already fixed.

Now, let's see why this warning message is not the way to go.

I have more than 1300 packages installed in the system, and I suspect
that most Debian users have a lot more.

If each and every of those packages sent me a warning just because
they are "old", Debian stable would become unusable and definitely not
nice.

And we don't want that, so I also second that this warning message
should be removed from the version in stable as well.

Thanks.

Acknowledgement sent to Samuel Thibault <sthibault@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 16:15:06 GMT) (full text, mbox, link).

Message #59 received at 819703@bugs.debian.org (full text, mbox, reply):

Jamie Zawinski, on Thu 31 Mar 2016 21:24:11 -0700, wrote:
> In the time it took me to read your whine, you could have upgraded your incredibly-out-of-date computer and saved us all the grief.

Incredibly-out-of-date?

I have hit the same exact bug this morning, while installing Debian
Jessie, which is the latest Debian stable release. It comes with version
5.30 of xscreensaver, which was released in september 2014, not even 2
years ago...  If you consider 2 years "incredibly-out of date", then do
not follow Debian bugs, since Debian is released about every 2 years...

As said in another mail in the thread, Debian users are supposed to
report bugs to the Debian BTS, to save you the old-bug reports. Then
it's up to Debian to backport whatever fix is needed if it feels to,
without upstream being involved at all.

The current check in the source code is 18 months, perhaps Debian could
patch it to raise it to 30 months, to cover the stable freeze+release
period?

Samuel

Message #64 received at 819703@bugs.debian.org (full text, mbox, reply):

Samuel Thibault, on Fri 01 Apr 2016 18:09:53 +0200, wrote:
> I have hit the same exact bug this morning, while installing Debian
> Jessie, which is the latest Debian stable release.

(That gives a really bad impression: Jessie is just one year old, we
told the installer to install the XFCE desktop, and the first thing we
got after rebooting from the installer was that fat warning...)

Samuel

Acknowledgement sent to Alexander Gerasiov <gq@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 16:33:04 GMT) (full text, mbox, link).

Message #69 received at 819703@bugs.debian.org (full text, mbox, reply):

Hello Samuel,

On Fri, 1 Apr 2016 18:09:53 +0200
Samuel Thibault <sthibault@debian.org> wrote:

> The current check in the source code is 18 months, perhaps Debian
> could patch it to raise it to 30 months, to cover the stable
> freeze+release period?

As for me, I'd suggest to turn this check off at all.

-- 
Best regards,
 Alexander Gerasiov

 Contacts:
 e-mail: gq@cs.msu.su  Homepage: http://gerasiov.net  Skype: gerasiov
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1

Acknowledgement sent to Holger Levsen <holger@layer-acht.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 16:57:07 GMT) (full text, mbox, link).

Message #74 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi,

IMO this warning should be patched away for the stable releases at
least. For the future I think either the same should be done or the
package dropped from Debian, as per the authors wishes.


-- 
cheers,
	Holger, switching to i3lock today

[signature.asc (application/pgp-signature, inline)]

Acknowledgement sent to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 16:57:10 GMT) (full text, mbox, link).

Message #79 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Fri, 1 Apr 2016 18:11:15 +0200 Samuel Thibault <sthibault@debian.org>
wrote:
> Samuel Thibault, on Fri 01 Apr 2016 18:09:53 +0200, wrote:
> > I have hit the same exact bug this morning, while installing Debian
> > Jessie, which is the latest Debian stable release.
> 
> (That gives a really bad impression: Jessie is just one year old, we
> told the installer to install the XFCE desktop, and the first thing we
> got after rebooting from the installer was that fat warning...)

Maybe the best course of action would be, if xfce didn't install
xscreensaver by default (but would choose a more lightweight / better
integrated alternative).


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #84 received at 819703@bugs.debian.org (full text, mbox, reply):

For those of you who can't be bothered to read the code, here's what the comment says.

I stand by my words here: If you are considering removing this warning, then I ask that instead, you remove the XScreenSaver software from Debian entirely. I believe Gnome-Screensaver will be more to your liking anyway.

/* If you are in here because you're planning on disabling this warning
before redistributing my software, please don't.

I sincerely request that you do one of the following:

1: leave this code intact and this warning in place, -OR-

2: Remove xscreensaver from your distribution.

I would seriously prefer that you not distribute my software at all
than that you distribute one version and then never update it for
years.

I am *constantly* getting email from users reporting bugs that have
been fixed for literally years who have no idea that the software
they are running is years out of date. Yes, it would be great if we
lived in the ideal world where people checked that they were running
the latest release before they report a bug, but we don't. To most
people, "running the latest release" is synonymous with "running the
latest release that my distro packages for me."

When they even bother to tell me what version they're running, I
say, "That version is three years old!", and they say "But this is
the latest version my distro ships". Then I say, "your distro
sucks", and they say "but I don't know how to compile from source,
herp derp I eat paste", and *everybody* goes away unhappy.

It wastes an enormous amount of my time, and kind of makes me regret
ever having released this software in the first place.

So seriously. I ask that if you're planning on disabling this
obsolescence warning, that you instead just remove xscreensaver from
your distro entirely. Everybody will be happier that way. Check
out gnome-screensaver instead, I understand it's really nice.

Of course, my license allows you to ignore me and do whatever the
fuck you want, but as the author, I hope you will have the common
courtesy of complying with my request.

Thank you!

jwz, 2014
*/

Acknowledgement sent to Yves-Alexis Perez <corsac@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 19:30:04 GMT) (full text, mbox, link).

Message #89 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On ven., 2016-04-01 at 18:54 +0200, Michael Biebl wrote:
> On Fri, 1 Apr 2016 18:11:15 +0200 Samuel Thibault <sthibault@debian.org>
> wrote:
> > 
> > Samuel Thibault, on Fri 01 Apr 2016 18:09:53 +0200, wrote:
> > > 
> > > I have hit the same exact bug this morning, while installing Debian
> > > Jessie, which is the latest Debian stable release.
> > (That gives a really bad impression: Jessie is just one year old, we
> > told the installer to install the XFCE desktop, and the first thing we
> > got after rebooting from the installer was that fat warning...)
> Maybe the best course of action would be, if xfce didn't install
> xscreensaver by default (but would choose a more lightweight / better
> integrated alternative).
> 
That's definitely something to consider for stretch. I wasn't really willing
to do that before because without having an Xfce locker I preferred staying
with the common ground, but I also had bad interaction with the upstream
developer and am not really interested in having more interactions.

Right now, there's a way to switch to something else, which is light-locker,
so it might be a good idea to do that indeed. I'll update the tasksel package
with that in mind.

Regards,
-- 
Yves-Alexis

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Fri, 01 Apr 2016 20:36:04 GMT) (full text, mbox, link).

Acknowledgement sent to Adam Borowski <kilobyte@angband.pl>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 20:36:04 GMT) (full text, mbox, link).

Message #94 received at 819703@bugs.debian.org (full text, mbox, reply):

On Fri, Apr 01, 2016 at 09:26:23PM +0200, Yves-Alexis Perez wrote:
> On ven., 2016-04-01 at 18:54 +0200, Michael Biebl wrote:
> > On Fri, 1 Apr 2016 18:11:15 +0200 Samuel Thibault <sthibault@debian.org>
> > > (That gives a really bad impression: Jessie is just one year old, we
> > > told the installer to install the XFCE desktop, and the first thing we
> > > got after rebooting from the installer was that fat warning...)

I wonder, perhaps this could warrant pushing an expedited update somehow?  A
popup blocking Xsession startup on every login shows Debian in a pretty bad
light.  Yeah, it's not a data-loss bug merely a bad PR bug but still...

> > Maybe the best course of action would be, if xfce didn't install
> > xscreensaver by default (but would choose a more lightweight / better
> > integrated alternative).
>
> That's definitely something to consider for stretch. I wasn't really willing
> to do that before because without having an Xfce locker I preferred staying
> with the common ground, but I also had bad interaction with the upstream
> developer and am not really interested in having more interactions.
> 
> Right now, there's a way to switch to something else, which is light-locker,
> so it might be a good idea to do that indeed. I'll update the tasksel package
> with that in mind.

light-locker has a hard dependency on lightdm, and if I read its description
right, it's impossible to remove.  I don't think we should tie xfce to a
single display manager.  It also does weird VT switching that's
disconcerting enough to be called a bug.

I took a look at alternatives:
* gnome-screensaver has OMGWTFBBQ-level insanity that makes it useless for
  anyone but Gnome3 lovers
* mate-screensaver isn't that much better (jwz is quite right...)
* cinnamon-screensaver is surprisingly sane.  Its depends/recommends would
  need trimming for reasonable use outside Cinnamon but I guess that's a
  matter of asking Cinnamon guys nicely.  After all, it wasn't envisioned
  to be used elsewhere...
* i3lock and slock[suckless-tools] lack a GUI

Another option could be forking xscreensaver, it could use some trimming and
fixing (for things where jwz disagreed).  (I don't volunteer here, though --
I see a bunch of things I could help with drive-by patching, but no full
maintenance, as I don't know xlib, details of DPMS handling or such).

So, other than the obvious "return 0;" fix in jessie, I'd recommend not
being hasty and think things through before updating all tasks, etc.

Meow!
-- 
A tit a day keeps the vet away.

Message #99 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Fri, 1 Apr 2016 10:10:40 -0700 Jamie Zawinski <jwz@jwz.org> wrote:
> For those of you who can't be bothered to read the code, here's what the comment says.
> 
> I stand by my words here: If you are considering removing this warning, then I ask that instead, you remove the XScreenSaver software from Debian entirely. I believe Gnome-Screensaver will be more to your liking anyway.

Sounds like we should do that indeed.
CCing our ftp-masters.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Acknowledgement sent to "Paul R. Tagliamonte" <paultag@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 01 Apr 2016 20:45:10 GMT) (full text, mbox, link).

Message #104 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Sadsies. xscreensaver is my screensaver of choice.

Sounds fine, let's file a RoM

Cheers,
  Paul

On Fri, Apr 1, 2016 at 4:37 PM, Michael Biebl <biebl@debian.org> wrote:

> On Fri, 1 Apr 2016 10:10:40 -0700 Jamie Zawinski <jwz@jwz.org> wrote:
> > For those of you who can't be bothered to read the code, here's what the
> comment says.
> >
> > I stand by my words here: If you are considering removing this warning,
> then I ask that instead, you remove the XScreenSaver software from Debian
> entirely. I believe Gnome-Screensaver will be more to your liking anyway.
>
> Sounds like we should do that indeed.
> CCing our ftp-masters.
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>


-- 
:wq

[Message part 2 (text/html, inline)]

Message #109 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

[note: if you don't CC: me, then I don't get your mail]

On Fri, 1 Apr 2016 22:33:31 +0200 Adam Borowski <kilobyte@angband.pl> wrote:
> On Fri, Apr 01, 2016 at 09:26:23PM +0200, Yves-Alexis Perez wrote:
> > That's definitely something to consider for stretch. I wasn't really willing
> > to do that before because without having an Xfce locker I preferred staying
> > with the common ground, but I also had bad interaction with the upstream
> > developer and am not really interested in having more interactions.
> > 
> > Right now, there's a way to switch to something else, which is light-locker,
> > so it might be a good idea to do that indeed. I'll update the tasksel package
> > with that in mind.
> 
> light-locker has a hard dependency on lightdm, and if I read its description
> right, it's impossible to remove.  I don't think we should tie xfce to a
> single display manager.  It also does weird VT switching that's
> disconcerting enough to be called a bug.

Xfce is not tied to lightdm or light-locker. Current situation is:

- task-xfce-desktop depends on xfce4, lightdm
- xfce4 depends on xfce4-session
- xfce4-session recommends xscreensaver

I've switched that (for stretch) to:

- task-xfce-desktop depends on xfce4, lightdm, light-locker
- xfce4 depends on xfce4-session
- xfce4-session recommends light-locker

So you'll have lightdm + light-locker by default when you select Xfce desktop
when installing, but you can remove it and if you manually install xfce4 and
don't install recommends you won't have it either.

Regards,
-- 
Yves-Alexis

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sat, 02 Apr 2016 00:15:11 GMT) (full text, mbox, link).

Acknowledgement sent to Jamil Said Jr. <jamilsaid@hotmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 00:15:11 GMT) (full text, mbox, link).

Message #114 received at 819703@bugs.debian.org (full text, mbox, reply):

Hello all,

I want to bring to your attention that LXDE is also affect by this. I am
also getting this disruptive and rude "warnings" every time that I start my
(fully updated, stable version) Debian Jessie LXDE computers.

It seems that the author does not understand (or doesn't care) that if you
use stable versions of Debian (and other distributions), it is because you
are willing to trade off "cutting edge" for stability. There are many, many
scenarios where the stable version is much preferred over the "latest"; as a
matter of fact, I almost always use and recommend stable versions.

I work with people who are quite "beginners" at using computers; many are
beginners at the level of not knowing to send email or even double-clicking
a .desktop file to launch an application - warnings like those implemented
on xscreensaver are bound to "scare" and "confuse" users of various levels
of knowledge, specially beginners. In addition to that (as others
commented), such warnings certainly make the OS less usable, and also cast a
bad light on the EXCELLENT Debian stable. This should be against policy, can
you imagine if all Debian packages start showing this kind of "warnings"?
The stable versions would be a mess.

I pledge to you to change the current (and future) xscreensaver versions on
Debian stable to make this "warnings" go away, as soon as possible.

Respectfully,
Jamil Said

Message #119 received at 819703@bugs.debian.org (full text, mbox, reply):

I meant:

"I plead to you to change the current (and future) xscreensaver versions on
Debian stable to make this "warnings" go away, as soon as possible."

Lol! Cheers,

Jamil Said

Acknowledgement sent to Daniel Shahaf <danielsh@apache.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 02:57:04 GMT) (full text, mbox, link).

Message #124 received at 819703@bugs.debian.org (full text, mbox, reply):

Control: found -1 5.30-1+deb8u1
Control: notfound -1 5.34-1

Axel Beckert wrote on Fri, Apr 01, 2016 at 09:54:39 +0200:
> Daniel Shahaf wrote:
> > P.S. I'm reporting this against the version in stable/jessie,
> 
> Sorry, you didn't. I've added the version (initially) in Jessie now.

Good catch, thank you.  I observed the prompts in the jessie-security
version but did not test the sid version; metadata updated accordingly.

> > diff --git a/driver/prefs.c b/driver/prefs.c
> > index 55bac7b..f9f96c3 100644
> > --- a/driver/prefs.c
> > +++ b/driver/prefs.c
> > @@ -1663,6 +1663,8 @@ stop_the_insanity (saver_preferences *p)
> >  Bool
> >  senescent_p (void)
> >  {
> > +  return 0;
> > +
> >    /* If you are in here because you're planning on disabling this warning
> >       before redistributing my software, please don't.
> 
> That doesn't fix the XFCE menu warning, too, right?

For future reference, this patch eliminates both of the prompts the
original report mentions.  (senescent_p() must return true for any of
the warnings to be displayed.)

To clarify: I'm simply stating a technical fact about the patch; I'm not
advocating one way or the other regarding whether the package should be
removed from stretch, since that's a political issue, as opposed
a technical one.  (jwz: the package cannot be removed from jessie and
earlier; it can only be removed from stretch and later.)

That said, for what it's worth, I think it would be unfortunate if the
package is removed from stretch: I run stable, it's a tradeoff
I consciously made, and there is no reason for me to be barred from
using software written by people who use their computers differently
than I do.

Cheers,

Daniel
(I wonder if I would be able to continue using unicode-screensaver under
light-locker, should xscreensaver be removed...)

No longer marked as found in versions xscreensaver/5.34-1. Request was from Daniel Shahaf <danielsh@apache.org> to 819703-submit@bugs.debian.org. (Sat, 02 Apr 2016 02:57:04 GMT) (full text, mbox, link).

Acknowledgement sent to Holger Levsen <holger@layer-acht.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 03:09:06 GMT) (full text, mbox, link).

Message #131 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi,

On Sat, Apr 02, 2016 at 02:53:30AM +0000, Daniel Shahaf wrote:
> Control: notfound -1 5.34-1

the bug is present in that version. The timebomb just hasn't been triggered
yet.

(Also for fixing this in stable (and oldstable) it needs to be fixed / not be
present in unstable first.)


-- 
cheers,
	Holger

[signature.asc (application/pgp-signature, inline)]

Message #136 received at 819703@bugs.debian.org (full text, mbox, reply):

Control: found -1 5.34-1

Holger Levsen wrote on Fri, Apr 01, 2016 at 23:04:28 -0400:
> Hi,
> 
> On Sat, Apr 02, 2016 at 02:53:30AM +0000, Daniel Shahaf wrote:
> > Control: notfound -1 5.34-1
> 
> the bug is present in that version. The timebomb just hasn't been triggered
> yet.

Okay; metadata restored.  (I had removed it because I had only confirmed
5.34-1 was affected by code inspection, as opposed to compiling/running
it and observing the message being displayed.)

Thanks,

Daniel

Marked as found in versions xscreensaver/5.34-1. Request was from Daniel Shahaf <danielsh@apache.org> to 819703-submit@bugs.debian.org. (Sat, 02 Apr 2016 03:12:03 GMT) (full text, mbox, link).

Acknowledgement sent to Adam Borowski <kilobyte@angband.pl>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 03:36:04 GMT) (full text, mbox, link).

Message #143 received at 819703@bugs.debian.org (full text, mbox, reply):

On Fri, Apr 01, 2016 at 11:04:28PM -0400, Holger Levsen wrote:
> On Sat, Apr 02, 2016 at 02:53:30AM +0000, Daniel Shahaf wrote:
> > Control: notfound -1 5.34-1
> 
> the bug is present in that version. The timebomb just hasn't been triggered
> yet.

For the record, the timebomb for 5.34 will go off on 2017-04-01, ie, shortly
after stretch's expected release date.

> (Also for fixing this in stable it needs to be fixed / not be present in
> unstable first.)

Why?  The fix is a trivial technical matter (Daniel's one-line patch in the
very first mail) and no one questions what to do for stable.

It's the political issue in unstable what needs deliberation.  And it looks
like removal is more likely to happen than forking, so the problem might
be never fixed in unstable.

> and oldstable

The timebomb was introduced in 5.21, oldstable has 5.15, o-o-stable 5.11, so
neither is affected.

-- 
A tit a day keeps the vet away.

Acknowledgement sent to Peter Nowee <peter@peternowee.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 03:51:04 GMT) (full text, mbox, link).

Message #148 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

I do not agree with the removal of the xscreensaver package.

Thankfully, when writing down his wish regarding this particular piece
of code, the author made sure to write that he did not mean to derogate
the user freedoms provided by the license he chose:

> Of course, my license allows you to ignore me and do whatever the
> fuck you want, but as the author, I hope you will have the common
> courtesy of complying with my request.

He just confirmed to us that he still stands by those words as well.

So, in the end, he values user freedom above his wish that we either
keep the warning or remove the software from our distribution. This
deserves our respect and gratitude.

Considering the issue at hand, I think we should exercise that user 
freedom now by disabling the warning while keeping the software in our 
distribution. For jessie/stable I think there is even no other choice.  

At the same time, we could try to make up for not having the "common
courtesy" he expected from us. For example, we could mention "Bug
reports:" with a Debian URL above his URL in the About dialog. I think
this would greatly reduce the number of bug reports on old versions
directed to him, which he named as the main reason behind his original
wish.

I hope this policy can then be extended to keep xscreensaver in future
Debian releases as well.

[signature.asc (application/pgp-signature, inline)]

Acknowledgement sent to Holger Levsen <holger@layer-acht.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 04:09:03 GMT) (full text, mbox, link).

Message #153 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi,

On Sat, Apr 02, 2016 at 05:33:52AM +0200, Adam Borowski wrote:
> > (Also for fixing this in stable it needs to be fixed / not be present in
> > unstable first.)
> Why? 

because that's the usual policy for fixing issues in stable, which was
also confirmed for this particular issue by a SRM on #debian-release
today.

> [...] it looks
> like removal is more likely to happen than forking, so the problem might
> be never fixed in unstable.

Removing the package from unstable will cause the bug not be present in
unstable so that's an ok solution from the POV of getting it fixed in
stable.

> The timebomb was introduced in 5.21, oldstable has 5.15, o-o-stable 5.11, so
> neither is affected.

Thanks for the clarification. (Also for checking when it will hit 5.34!)

-- 
cheers,
	Holger

[signature.asc (application/pgp-signature, inline)]

Acknowledgement sent to Jamie Zawinski <jwz@jwz.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 04:09:05 GMT) (full text, mbox, link).

Message #158 received at 819703@bugs.debian.org (full text, mbox, reply):

Please remove XScreenSaver from Debian.

Peter Nowee, please take your sanctimony and go fuck yourself with it.

Message #163 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Fri, Apr 01, 2016 at 09:04:45PM -0700, Jamie Zawinski wrote:
> Please remove XScreenSaver from Debian.
> 
> Peter Nowee, please take your sanctimony and go fuck yourself with it.
> 

Was I wrong when I said that you value user freedom above your wish
that we either keep the warning or remove your software from Debian?

I mean, you are the one giving mixed signals here: First telling us we
can use, modify and distribute your work, then asking us to "please"
not modify this and "please" not distribute that.

Just change your license if this is really as important to you as your
cursing suggests.

[signature.asc (application/pgp-signature, inline)]

Message #168 received at 819703@bugs.debian.org (full text, mbox, reply):

Peter Nowee wrote:

> Was I wrong when I said that you value user freedom above your wish
> that we either keep the warning or remove your software from Debian?

Awesome, you seem to be one of those people who think "if it's legal, it must be right." That's a common toxin in the software industry these days.

I guess you want Debian to be the kind of operation that uses the work of others while blatantly and explicitly ignoring the wishes of the person who *did the actual creative work*.

Nice. 

--
Jamie Zawinski      https://www.jwz.org/      https://www.dnalounge.com/

Message #173 received at 819703@bugs.debian.org (full text, mbox, reply):

In case you decide to remove xscreensaver from future Debian distributions,
I have a suggestion:

On whatever substitutes xscreensaver, I would like to suggest that you
include the option to turn the screen "blank" in addition to "turn screen
off" when the screensaver kicks in. Some screensavers just turn the screen
off, and upon restart of the screen, some hardware crashes (sometimes
intermittently) and renders the computer unusable. I've seen quite a bit of
that.

Also, I want to point out that I am very in favor of eliminating this rude &
disruptive "warning" ASAP from stable and all other Debian branches. If you
release code with a free, open source license, you must understand and be
prepared that your code may be modified and used as other users see fit.

Cheers,
Jamil

Message #178 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Fri, Apr 01, 2016 at 10:37:35PM -0700, Jamie Zawinski wrote:
> Peter Nowee wrote:
>
> > Was I wrong when I said that you value user freedom above your wish
> > that we either keep the warning or remove your software from Debian?
>
> Awesome, you seem to be one of those people who think "if it's legal,
> it must be right." That's a common toxin in the software industry
> these days.
>
> I guess you want Debian to be the kind of operation that uses the
> work of others while blatantly and explicitly ignoring the wishes of
> the person who *did the actual creative work*.

No and no.

You called this upon yourself when you put in that time bomb.

With regard to stable/jessie, I propose we use our rights, but try to 
make up for ignoring your wishes by trying to reduce the flow of bug 
reports to you in another way, for example by the additional URL in the
About box I suggested by my earlier email. Please reconsider.

With regard to future versions of Debian, again I think you should be 
more clear in your license terms. Don't pretend to publish it as free 
software, but then use pretty "please", time bombs and cursing to get
users to not use their freedoms.

[signature.asc (application/pgp-signature, inline)]

Acknowledgement sent to Benjamin Moody <benjamin.moody@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 07:09:04 GMT) (full text, mbox, link).

Message #183 received at 819703@bugs.debian.org (full text, mbox, reply):

To JWZ: if you don't wish to read about issues like this one, please
stop reading Debian bug reports.  There's no need for you to do so; if
and when an issue arises in a Debian bug report that requires action
from you, you _will_ hear about it.

To everyone:

What about renaming the package, along the lines of iceweasel (i.e.,
"fork in name only")?  If JWZ's frustration is due to clueless users
contacting him directly about bugs in Debian, then renaming the
program would presumably help in redirecting those users' complaints
to the place they belong.

Of course, it's important to keep the existing attribution notices
(unless the author prefers otherwise), but adding additional comments
alongside them, reminding users of where to report bugs, would
certainly also be helpful.

Acknowledgement sent to Andriy Grytsenko <andrej@rep.kiev.ua>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 08:57:06 GMT) (full text, mbox, link).

Message #188 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

I completely agree with blaming upstream to be ignorant so renaming the
package would be wise when working with such upstream.

I also think this bug severity is 'important', not 'normal' since it
affects usability of package, at least it confuses users. If I was the
maintainer of this package then I would raise the severity.

[signature.asc (application/pgp-signature, inline)]

Severity set to 'important' from 'normal' Request was from Axel Beckert <abe@debian.org> to control@bugs.debian.org. (Sat, 02 Apr 2016 09:03:04 GMT) (full text, mbox, link).

Acknowledgement sent to Axel Beckert <abe@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 09:06:12 GMT) (full text, mbox, link).

Message #195 received at 819703@bugs.debian.org (full text, mbox, reply):

Hi,

Andriy Grytsenko wrote:
> I completely agree with blaming upstream to be ignorant

Definitely.

> so renaming the package would be wise when working with such
> upstream.

What about yscreensaver? ;-)

> I also think this bug severity is 'important', not 'normal' since it
> affects usability of package, at least it confuses users. If I was the
> maintainer of this package then I would raise the severity.

I've allowed myself to bump the severity to important. It's also
already mentioned in #debian-devel's /topic. That usually only happens
with bugs with a heavy impact (independent of being trivial to fix or
not).

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sat, 02 Apr 2016 11:15:03 GMT) (full text, mbox, link).

Acknowledgement sent to Melleus <melleus@openmailbox.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 11:15:03 GMT) (full text, mbox, link).

Message #200 received at 819703@bugs.debian.org (full text, mbox, reply):

The situation is very simple in fact. Somebody just lost the ground and
cannot see the difference between the free software authorship, credit
for it and property rights no more. He accepts the free license but in a
some strange one-way fashion: to get the freedom for himself and to take
it away from the others. Just like terrorists do. Setting timebombs and
objecting others to disable those bombs is not only the violation of
free software license as up to me, but also it spoils the idea of the
free software itself. Now I see how great is the idea behind the GPL.

Acknowledgement sent to Hilko Bengen <bengen@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 12:39:08 GMT) (full text, mbox, link).

Message #205 received at 819703@bugs.debian.org (full text, mbox, reply):

* Paul R. Tagliamonte:

> Sadsies. xscreensaver is my screensaver of choice.
>
> Sounds fine, let's file a RoM

Wouldn't it be better to first focus on the imminent problem that users
are facing? As of today, xscreensaver as shipped with jessie annoys
users and that needs to stop.

So the upstream author has shown that he enjoys being a dick and that he
can't be bothered to deal with users' bug reports against versions of
his software that he no longer wants to support. Apparently, giving
canned responses to those users takes too much of his time, while
spewing individual insults here does not.

Why should we or our users care about any of this? We should simply
patch out those stupid warnings, maybe even leave a note in
README.Debian for interested users to read, and be done with it.

I don't see a good substitute for xscreensaver in Debian at the moment:
i3lock, slock, etc. are too bare-bones and don't really work for
unexperienced users, not sure about light-locker because of the ligthdm
dependency. Please, let's not remove xscreensaver just yet: The software
itself is stable and looks otherwise perfectly maintainable for people
who can ignore the author's occasional tirade.

Cheers,
-Hilko

Message #210 received at 819703@bugs.debian.org (full text, mbox, reply):

Hi,

Paul R. Tagliamonte wrote:
> Sadsies. xscreensaver is my screensaver of choice.

Same here since xlockmore was removed due to unreliability and hence
security-relevant RC bugs.

> Sounds fine, let's file a RoM

Are you nuts? You just said, it's your favourite! Why do you want to
kill it?

Hilko Bengen wrote:
> Wouldn't it be better to first focus on the imminent problem that users
> are facing?

Definitely.

> Why should we or our users care about any of this?

We shouldn't. We should focus on the distribution _we_ want to use[0],
not on what some crazy upstreams think we should do or now.

[0] http://www.eyrie.org/~eagle/journal/2012-01/004.html

> We should simply patch out those stupid warnings, maybe even leave a
> note in README.Debian for interested users to read, and be done with
> it.

Another option which should satisfy both, upstream and users is to
offer users the choice to use a backport of xscreensaver. But I'm
personally totally fine with having an 18 months old xscreensaver in
Stable. As I am with nearly all other packages. I mean, it's Stable,
not bleeding edge.

> I don't see a good substitute for xscreensaver in Debian at the moment:
> i3lock, slock, etc. are too bare-bones and don't really work for
> unexperienced users,

And gnome-screensaver (which looks like a fork of xscreensaver) lacks
quite some features like "xscreensaver-command -watch" while adding
additional and completely unnecessary dependencies on GNOME stuff
non-GNOME users don't need.

> Please, let's not remove xscreensaver just yet:

+1

> The software itself is stable and looks otherwise perfectly
> maintainable for people who can ignore the author's occasional
> tirade.

Well, if upstream can't communicate in a sane and polite manner and
continues to write such hate mails, there's still the possibility of
banning him from the BTS.

Just because some upstream hasn't read
https://www.debian.org/doc/manuals/debian-faq/ch-choosing.en.html#s3.1.3
doesn't mean that we should remove all his packages from Debian.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Acknowledgement sent to Paul Tagliamonte <paultag@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 13:57:03 GMT) (full text, mbox, link).

Message #215 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Sat, Apr 02, 2016 at 03:17:11PM +0200, Axel Beckert wrote:
> > Sounds fine, let's file a RoM
> 
> Are you nuts? You just said, it's your favourite! Why do you want to
> kill it?

Well, yes, I am a bit nuts, but here's why.

I think we can all agree the current situation is broken. Fixes in newer
versions aren't getting backported, which means either the maintainer
isn't interested in backporting bugfixes to stable (it's a lot of work,
I understand it), or users don't report bugs to the BTS, going right
upstream, and the maintainer isn't aware of them (which might explain
why upstream is seeing bugs from users in Ubuntu and Debian).

Even if it's just from testing and the next stable release.

However, ore and more, I'm becoming a bit concerend about leaf packages
we maintain in stable that have their own release schedule, where they
do significat testing to ensure no regressions or breakages. We don't
have a good story for updating a package like this (short of backports,
but even that isn't a clear win).

This wouldn't be the first removal because an upstream isn't happy, and
it won't be the last.

At the very least, CC'ing ftpmaster@ and asking what they think, the
obvious response is "Sure, remove it".

I'm not going to tell someone with any fancy hat I might have hanging up
to maintain something against their will, or back a decision to piss off
your upstream.

So, let's make a deal. I see a two outcomes that are tolerable:

  - ${BUGS} in xscreensaver get a backport to the version in stable, and
    a s-p-u, and upstream tells distro users to report bugs with the distros.

  - xscreensaver is removed from stable, unstable stays up to date. This
    doesn't make upstream happy until next release.

The SRMs might have something to say about the first ("Is this a RC bug,
why are you backportting a papercut bug"), and I've started to become
annoyed with the second type of package.

Anyway, my two cents. This entire discussion appears to be a pit of
angry emotions and no real communication. That's a shame. So this will
be the last I'll say on this until (if?) you file a RoM. In that case,
likely dak will reply on my behalf.

Cheers,
  Paul

[signature.asc (application/pgp-signature, inline)]

Acknowledgement sent to Santiago Vila <sanvila@unex.es>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 16:06:03 GMT) (full text, mbox, link).

Message #220 received at 819703@bugs.debian.org (full text, mbox, reply):

On Sat, Apr 02, 2016 at 11:03:58AM +0200, Axel Beckert wrote:

> Andriy Grytsenko wrote:
>
> > so renaming the package would be wise when working with such
> > upstream.
> 
> What about yscreensaver? ;-)

Some more ideas:

"tsfkax" for "The Screensaver Formerly Known As Xscreensaver"

"xxscreensaver" for "ex-xscreensaver".


Thanks.

Message #225 received at 819703@bugs.debian.org (full text, mbox, reply):

First and foremost I am for fixing the stable version as soon as possible
(by fixing I mean remove the offending warnings). The maximum priority here,
in my view, it is to ensure that the people who depends on Debian stable can
get rid of these rude and disruptive warnings (which will scare and confuse
many), and that should be done in a regular update that can be applied via a
conservative apt-get update. Then I am for fixing all branches as well.

Then I believe we should NOT remove this package, just rename it in the next
version of Debian. Why throw away this good code? It serves people well! The
author desire is clearly out-of-touch, as he ignores that stable branches
are deliberately kept with older versions in name of better stability - his
position is untenable, and his behavior is less than polite (to put it
mildly). He released the code under a free, open source license, so heck
yeah we can change it.

For the record however, I want to thank the author for his good work on this
package - it is not easy to do what he did. I also understand his concerns,
but quite frankly, I believe this issue is one that he has to deal with
himself - maybe just have an specific email address for bugs, with a canned
automated response which could say something like this:

"Hello, thank you for reporting this problem and thus helping to improve
xscreensaver. I review all emails, but please keep in mind this: Many Linux
distributions ship older versions of this software; maybe the issue that you
are reporting is already fixed in a new release. Please check the following
link www.link.com to see the changelog (things that were fixed already in
previous versions), and if you see your problem there, then you should know
that you must get a updated version from this software. PLEASE NOTE THAT I
AM UNABLE TO ANSWER EMAILS RELATED TO BUGS THAT HAVE ALREADY BEEN FIXED. If
the bug is new, I will get back to you. Cheers."

Problem solved! I hope that the author is reading this and will reconsider
his position. I for one appreciate his work and I would prefer that he
continues to be part of and contribute to Debian.

My 2 cents.

Jamil

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sat, 02 Apr 2016 22:30:04 GMT) (full text, mbox, link).

Acknowledgement sent to jsmith@resonatingmedia.com:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 02 Apr 2016 22:30:04 GMT) (full text, mbox, link).

Message #230 received at 819703@bugs.debian.org (full text, mbox, reply):

I think a few things could be done with Xscreensaver which would be
better than removing the package (which I use and enjoy) from Debian.

For example:

1. Yes, let's remove the pop-up, it's really annoying, offers an
impractical suggestion and does not accomplish for most users.

2. Why not remove the author's e-mail address from the Help->About menu?
Leave the name so proper credit is given, but remove the e-mail address.
In its place, put a link to the Debian bug tracker. Then the author
won't get flooded with bug reports and bugs can be properly handled
here, downstream. After all, people are not likely to e-mail someone if
they don't have the e-mail address.

3. Possibly rename the Debian package so that searches for it don't lead
back to the author's website/e-mail. I liked someone else's suggestion
of ex-screensaver.

With the above three actions it should remove almost all bug reports
against older versions (for the author), prevent Debian users from
seeing the annoying pop-up and allow everyone to keep using the software.

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sun, 03 Apr 2016 01:24:03 GMT) (full text, mbox, link).

Acknowledgement sent to Alfie John <alfie@alfie.wtf>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 01:24:03 GMT) (full text, mbox, link).

Message #235 received at 819703@bugs.debian.org (full text, mbox, reply):

>> so renaming the package would be wise when working with such
>> upstream.
>
> What about yscreensaver? ;-)

If you're looking for something really light, the suckless-tools package is
already in the repo, and has a utility called slock that does what I want.

Alfie

-- 
Alfie John
https://www.alfie.wtf

Acknowledgement sent to SilvioTO <silvioto@riseup.net>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 08:15:03 GMT) (full text, mbox, link).

Message #240 received at 819703@bugs.debian.org (full text, mbox, reply):

This warning is offensive, expecially to the new end users, for 
professionals that installed them, and Debian community in general. 
Please remove.

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sun, 03 Apr 2016 14:12:04 GMT) (full text, mbox, link).

Acknowledgement sent to Bjørn Mork <bjorn@mork.no>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 14:12:05 GMT) (full text, mbox, link).

Message #245 received at 819703@bugs.debian.org (full text, mbox, reply):

Package: xscreensaver
Version: 5.34-1
Followup-For: Bug #819703

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Why is this a bug? Is there something not working? AFAICS, this is a
documented feature. Whether you like the feature or not is irrelevant.
In any case, how the heck can anyone justify an "important" severity? I.e.

 a bug which has a major effect on the usability of a package, without
 rendering it completely unusable to everyone.

Please explain how this warning affects the usability of the package,
or downgrade this bug to the more appropriate "wishlist" severity.

I'm really surprised seeing requests for package removal based on this
"bug".  Is this now RC?  Are there anyone forcing you to use this
package?  I humbly request that xscreensaver is kept in Debian.  For me,
it is the only acceptable screensaver, for this reason among others:
https://www.jwz.org/xscreensaver/toolkits.html

If any of you care about screen savers in Debian, then your time is much
better spent auditing the other screen saver packages.

Thanks.


Bjørn


-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlcBIakACgkQ10rqkowbIsnC5wCfUgoJfe0Bk7KrPl8PP3may7tR
fBwAoIwSuBrjyX7ZPDeD/Z1WXW5+Ursi
=O0ju
-----END PGP SIGNATURE-----

Acknowledgement sent to Hilko Bengen <bengen@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 14:51:09 GMT) (full text, mbox, link).

Message #250 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

* Jesse Smith:

> 2. Why not remove the author's e-mail address from the Help->About menu?
> Leave the name so proper credit is given, but remove the e-mail address.

Yes! Thank you, I think this is a simple, brilliant idea. After all,
JWZ's main complaint seems to be that people bother him about old
xscreensaver versions via e-mail.

I have prepared a patch that removes the e-mail address (but not the
name) form all binaries, scripts, and manpages.

To be sure, I've also added some grep to debian/rules that checks the
directories from which the binary packages are built (before dh_compress
runs).

Cheers,
-Hilko

[91_remove_jwz_email.patch (text/x-diff, attachment)]

[Message part 3 (text/x-diff, attachment)]

Acknowledgement sent to Santiago Vila <sanvila@unex.es>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 14:57:06 GMT) (full text, mbox, link).

Message #255 received at 819703@bugs.debian.org (full text, mbox, reply):

On Sun, Apr 03, 2016 at 03:59:11PM +0200, Bjørn Mork wrote:

> Why is this a bug?

Quite simply: Because packages in Debian should not be telling the
user "you should upgrade me".

In particular, packages in Debian stable should not suggest that they
need upgrading "for the sake of upgrading".

For a third-party application in a Windows environment, it may make
sense for an application to say "upgrade me". For a system like Debian
where everything is under the control of the package manager, it does
not make sense.

> Is there something not working? AFAICS, this is a documented feature.

Documenting a misfeature does not necessarily make it a desirable feature.

Debian stable is frozen. There is no point in upgrading something just
"because it's old". We already know it's old and we are ok with that.

Moreover, Debian aims to be an universal operating system, not just
for desktops, not just for servers. Think about an application telling
you "please upgrade me" while you are in Mars...

> Whether you like the feature or not is irrelevant.

Actually, it's not irrelevant at all. If we don't like a "feature", or
it does not suit the needs of our users, it's completely fine that we
remove the feature, the same way we can add a feature not present in
the original code if we think it makes the program better.

For example, Firefox in Windows has a button to upgrade it. Because we
have a package manager which handles all upgrades, you will not see
such button in the Debian version of Firefox (be it Iceweasel or
Firefox in testing).

That's the point of software freedom, to be able to modify, adapt,
improve and fix bugs in the software, regardless of those bugs being
accidental or (as in this case) intentional.

Thanks.

Acknowledgement sent to alberto fuentes <pajaro@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 15:57:13 GMT) (full text, mbox, link).

Message #260 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

A shame that Jamie didnt try to work a solution out with the debian
maintainer instead of the aggressive time bomb...

Also a shame that some maintainers kneejerk reaction to just have it out

Both sides saying indirectly, im big enough and i dont need you

Developers love to have users and users love to use best programs. We are
all in the same boat here after all

As its been already mention, just renaming the program to something like
debian-screensaver (i prefer descriptive names to fun puns) should fix
it... or maybe if upstream prefer we keep the name, we can add a second
line after his email explicitly stating that the bugs should go to our bts
and not upstream

We already do that in projects like kodi...

Probably someone as smart as Jamie can come up with even better solution
that makes him happy and dont waste his time, so we can distribute his
software in the best possible way. We only want to help here and I hope we
can reach an agreement for this particular software, since this is a
recursive problem for linux distributions

We all know about the infamous "debian seems to turn simplest things into
big problems" problem, but im proud of what we try to achieve underneath...
make everything work together, so I ask you Jamie to be patient with us :)


Cheers

[Message part 2 (text/html, inline)]

Acknowledgement sent to Tiago Ilieve <tiago.myhro@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 17:15:04 GMT) (full text, mbox, link).

Message #265 received at 819703@bugs.debian.org (full text, mbox, reply):

Hi Yves-Alexis,

On Fri, 01 Apr 2016 21:26:23 +0200 Yves-Alexis Perez <corsac@debian.org> wrote:
> Right now, there's a way to switch to something else, which is light-locker,
> so it might be a good idea to do that indeed. I'll update the tasksel package
> with that in mind.

Indeed. For someone who uses Xfce and rely on xscreensaver only for
locking, it's a matter of switching to light-locker and uncommenting
the line "greeter-hide-users=false" in "/etc/lightdm/lightdm.conf".
This way it behaviors in a way pretty close to the former.

Thanks for the suggestion.

Regards,
Tiago.

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Acknowledgement sent to Wolfgang Roessler <wolfg-roe@t-online.de>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 18:39:07 GMT) (full text, mbox, link).

Message #270 received at 819703@bugs.debian.org (full text, mbox, reply):

I requested (per email) friendly to jwz, how to deactivate the warning
pop-up. And wrote him, that I don't need this pop-up.
Jwz sassed only:"Upgrade to a version that is not years out of date. If
the distro you have chosen makes it difficult for you to do so, you have
chosen a poor distro."
No comment to such a "nice" developers answer.
Please, Debian-maintainers/-developers go ahead for removing this
pointless warning pop-up.
Thanks.
Wolfgang Roessler.

--
wolfg-roe@t-online.de

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sun, 03 Apr 2016 21:27:10 GMT) (full text, mbox, link).

Acknowledgement sent to Jeff Warnica <jeff@coherentnetworksolutions.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 21:27:10 GMT) (full text, mbox, link).

Message #275 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

There is the third option of "actually back port fixes and thus honestly be
able to remove the obsolete software warning" which should be investigated.

Just selecting a random version and never changing it may quality as
"stable", but that isn't "useful".

[Message part 2 (text/html, inline)]

Acknowledgement sent to Michael Greger <miskatonicdad@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 21:42:12 GMT) (full text, mbox, link).

Message #280 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Here's a patch to remove the obsolensence checking that xscreensaver does.

Currently there's no way for a user to disable or prevent the annoying
popups everytime their system starts.

Amazingly bad idea.

[Message part 2 (text/html, inline)]

[xscreensaver.patch (text/x-diff, attachment)]

Acknowledgement sent to Axel Beckert <abe@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 22:24:04 GMT) (full text, mbox, link).

Message #285 received at 819703@bugs.debian.org (full text, mbox, reply):

Hi Jeff,

Jeff Warnica wrote:
> There is the third option of "actually back port fixes and thus honestly be
> able to remove the obsolete software warning" which should be investigated.

Nope, that's _not_ an option for Debian Stable. Please read
https://www.debian.org/doc/manuals/debian-faq/ch-choosing.en.html#s3.1.3

> Just selecting a random version and never changing it may quality as
> "stable",

That's the point.

> but that isn't "useful".

It's as useful as on the first day where the Debian Stable release has
been released. New features will very likely introduce bugs and bugs
reduce usability usually more than missing new features.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Message #290 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Upstream is adamant that he gets bug reports (and all bug reports are
security bug reports, especially on security software) against the version
included with Debian, which have since been fixed.

Debian applies changed *all the time* to "stable" packages. The alternative
proposal is to apply changes to "stable" software.

Some ideal universe xscreensaver might maintain an active version and a
version for Debian. They don't, and aren't unique in their indifference to
the stated policies.

If you don't change things, fine, don't change things including the feature
warning that the software is obsolete.

If you do change things, then backport security fixes, however hard that
may be.

The laziest possible option is to remove the legitimate warning that the
software is obsolete.
On Apr 3, 2016 15:21, "Axel Beckert" <abe@debian.org> wrote:

> Hi Jeff,
>
> Jeff Warnica wrote:
> > There is the third option of "actually back port fixes and thus honestly
> be
> > able to remove the obsolete software warning" which should be
> investigated.
>
> Nope, that's _not_ an option for Debian Stable. Please read
> https://www.debian.org/doc/manuals/debian-faq/ch-choosing.en.html#s3.1.3
>
> > Just selecting a random version and never changing it may quality as
> > "stable",
>
> That's the point.
>
> > but that isn't "useful".
>
> It's as useful as on the first day where the Debian Stable release has
> been released. New features will very likely introduce bugs and bugs
> reduce usability usually more than missing new features.
>
>                 Regards, Axel
> --
>  ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>   `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
>

[Message part 2 (text/html, inline)]

Message #295 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Sun, Apr 03, 2016 at 05:39:49PM -0400, Michael Greger wrote:
> Here's a patch to remove the obsolensence checking that xscreensaver does.

For an upload to stable-proposed-updates, the release managers
appreciate that diffs are as small and easy to understand as possible,
so the shorter the diff, the better.

I would apply one of the following patches.

(The not-so-short version does not even modify the senescent_p()
function)

Thanks.

[using-old-software-is-ok.patch.txt (text/plain, attachment)]

[using-old-software-is-ok.short-version.patch.txt (text/plain, attachment)]

Message #300 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Sorry, the not-so-short patch would be like this.

[using-old-software-is-ok.patch.txt (text/plain, attachment)]

Message #305 received at 819703@bugs.debian.org (full text, mbox, reply):

Hi Santiago,

Santiago Vila wrote:
> Sorry, the not-so-short patch would be like this.

That edits four files. The patch posted in the initial bug report
(https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;att=1;filename=patch.txt;bug=819703)
only added a single line ("return 0" to senescent_p()) and as far as I
can see it should suffice for all places where you removed the call to
senescent_p():

diff --git a/driver/prefs.c b/driver/prefs.c
index 55bac7b..f9f96c3 100644
--- a/driver/prefs.c
+++ b/driver/prefs.c
@@ -1663,6 +1663,8 @@ stop_the_insanity (saver_preferences *p)
 Bool
 senescent_p (void)
 {
+  return 0;
+
   /* If you are in here because you're planning on disabling this warning
      before redistributing my software, please don't.
 
		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Acknowledgement sent to Adam Borowski <kilobyte@angband.pl>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 23:30:03 GMT) (full text, mbox, link).

Message #310 received at 819703@bugs.debian.org (full text, mbox, reply):

On Sun, Apr 03, 2016 at 03:44:55PM -0700, Jeff Warnica wrote:
> Upstream is adamant that he gets bug reports (and all bug reports are
> security bug reports, especially on security software) against the version
> included with Debian, which have since been fixed.

There are two ways jwz can get such bug reports:
* from the BTS -- ie, with an explicit opt-in.  If this hurts, "don't do
  that, then".
* via e-mail: in that case, the software shouldn't advertise his address,
  as name or nick is adequate to show authorship.  This doesn't apply for
  all people -- for example, there are many politicians, film directors,
  even software developers named "Adam Borowski", but "Jamie Zawinski"
  seems to be google-unique for as many pages as I checked.[1]

Another possible concern is that he doesn't want his name associated with
"obsolete" versions.  In such case, a rename would work.

jwz: could you tell us which of these concerns apply?

> Debian applies changed *all the time* to "stable" packages. The alternative
> proposal is to apply changes to "stable" software.

Only for security and selected RC bugs.

> If you do change things, then backport security fixes, however hard that
> may be.

Which Debian does!  It's exactly what a stable release is about.

> The laziest possible option is to remove the legitimate warning that the
> software is obsolete.

The software is not obsolete, it's fully working and at least as secure as
the newest shiniest release.  It does receive security updates, and the code
had more time for bugs to surface.

[1]. There's 1082 times as many people named Borowski than Zawi[nń]ski,
having a Polish surname but non-Polish first name makes the combination
rare, and yeah, jwz having a wee more claims for fame than me might also
be a factor.
-- 
A tit a day keeps the vet away.

Acknowledgement sent to Alexander Gerasiov <gq@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 03 Apr 2016 23:42:03 GMT) (full text, mbox, link).

Message #315 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hello Santiago,

On Mon, 4 Apr 2016 01:02:01 +0200
Santiago Vila <sanvila@unex.es> wrote:

> On Sun, Apr 03, 2016 at 05:39:49PM -0400, Michael Greger wrote:
> > Here's a patch to remove the obsolensence checking that
> > xscreensaver does.
> 
> For an upload to stable-proposed-updates, the release managers
> appreciate that diffs are as small and easy to understand as possible,
> so the shorter the diff, the better.
> 
> I would apply one of the following patches.

This one is better:


-- 
Best regards,
 Alexander Gerasiov

 Contacts:
 e-mail: gq@cs.msu.su  Homepage: http://gerasiov.net  Skype: gerasiov
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1

[xscreensaver-short.patch (text/x-patch, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Mon, 04 Apr 2016 00:39:20 GMT) (full text, mbox, link).

Acknowledgement sent to Santiago Vila <sanvila@unex.es>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Mon, 04 Apr 2016 00:39:20 GMT) (full text, mbox, link).

Message #320 received at 819703@bugs.debian.org (full text, mbox, reply):

On Mon, Apr 04, 2016 at 01:26:17AM +0200, Axel Beckert wrote:
> Hi Santiago,
> 
> Santiago Vila wrote:
> > Sorry, the not-so-short patch would be like this.
> 
> That edits four files.

Yes, I know, but the function says "leave this code intact and this
warning in place" :-)

In the unlikely case that we wanted to follow that to the letter,
we could stop calling the function instead. Doing that would also
highlight the places at which the time bomb was intended to be
triggered in the code.

Of course, we would be honoring the letter but not the "spirit",
so I don't really think the not-so-short patch will make the author
happy.

Thanks.

Acknowledgement sent to Peter Lawler <bleeter@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Mon, 04 Apr 2016 00:42:04 GMT) (full text, mbox, link).

Message #325 received at 819703@bugs.debian.org (full text, mbox, reply):

On Fri, 1 Apr 2016 10:10:40 -0700 Jamie Zawinski wrote:
> For those of you who can't be bothered to read the code, here's what 
the comment says.

<snip>

Sounds awfully a lot like this old Gentoo bug

https://bugs.gentoo.org/show_bug.cgi?id=35890

And yes, I'm probably going to hell for submitting this into the report...

Pete.

Acknowledgement sent to Marc Haber <mh+debian-packages@zugschlus.de>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Mon, 04 Apr 2016 06:57:03 GMT) (full text, mbox, link).

Message #330 received at 819703@bugs.debian.org (full text, mbox, reply):

On Sun, Apr 03, 2016 at 03:44:55PM -0700, Jeff Warnica wrote:
> If you do change things, then backport security fixes, however hard that
> may be.

That would not fix the issue as the software still has the old version
number and the warning.

Additionally, friendly upstreams tag security fixes as such in the
actual commit/patch.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Mon, 04 Apr 2016 15:21:09 GMT) (full text, mbox, link).

Message #335 received at 819703@bugs.debian.org (full text, mbox, reply):

On Fri, 1 Apr 2016, Jamie Zawinski wrote:

> Awesome, you seem to be one of those people who think "if it's
> legal, it must be right." That's a common toxin in the software
> industry these days.

Speaking of right and wrong:

Have you considered to change the license, so that it better reflects
what it's right and what it's wrong?

We have "main" and "non-free" sections in the repositories.

But we don't have a "morally-non-free" section for software which is
legally free to distribute, but "wrong" to modify according to the author.
[ For this reason ftpmaster will probably just remove this from Debian ].

So: What would be the problem in actually forbidding to remove the warning?

More than one copyright holder? In such case: who of them are to
decide what's "right" and what's "wrong"? It is easy to imagine that
some contributions were made on the basis that the program would be free,
both in the legal sense and the moral sense.

Thanks.

Acknowledgement sent to ireulx <ireulx@hotmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Mon, 04 Apr 2016 15:51:08 GMT) (full text, mbox, link).

Message #340 received at 819703@bugs.debian.org (full text, mbox, reply):

When did the Free Software Community come to mean Debian users?
When did 'needs' come to mean 'wants'?

Debian Social Contract (1997)
-----------------------------
We will support people who create or use both free and non-free works on Debian.
We will be guided by the needs of our users and the free software community.

Debian Social Contract (2016)
-----------------------------
We will support people who use Debian.
We will be guided by the wants of our users.
When a creator that has been part of the free software community for decades
makes a polite request we will tell them that they "obviously haven't understood
how distributions work and what stable releases are" (i.e. that they need to
conform to our way of doing things).
We will then change their code against their wishes and call them "ignorant",
"stubborn", "crazy" and a "dick."
We will focus on the distribution _we_ want to use, not on the broader free
software community.
P.S. Our petty wants are more important than upstream's needs.

Acknowledgement sent to alberto fuentes <pajaro@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Mon, 04 Apr 2016 19:21:10 GMT) (full text, mbox, link).

Message #345 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Mon, Apr 4, 2016 at 5:17 PM, Santiago Vila <sanvila@unex.es> wrote:

> Speaking of right and wrong:
>
> Have you considered to change the license, so that it better reflects
> what it's right and what it's wrong?
>

Please, dont turn this into something about morale or licenses.

This is one of those rare cases that can be fixed technically.

So far, upstream just wishes not be bothered about what debian does with
his software and rightfully so

He just chose a rather aggressive way to communicate the problem that
debian was causing him using a nagging text

Lets just find a way where our users stop pestering him and call it a day...

This happens all the time in all the projects

[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Mon, 04 Apr 2016 20:30:15 GMT) (full text, mbox, link).

Message #350 received at 819703@bugs.debian.org (full text, mbox, reply):

Hello Alberto.

On Mon, Apr 04, 2016 at 09:17:23PM +0200, alberto fuentes wrote:

> Please, dont turn this into something about morale or licenses.

I don't see the "turn". As I see it, it's a morale and licenses
problem from the beginning: The program itself is free, but the author
asks that we do not modify a certain part of it.

That would be a "moral dilemma". Usually, moral dilemmas like that are
resolved by ftpmasters removing the package from Debian.

> This is one of those rare cases that can be fixed technically.
> 
> So far, upstream just wishes not be bothered about what debian does with
> his software and rightfully so

Actually, his wishes are expressed in the ten first lines of
senescent_p(). The remaining text is just the "rationale".

> He just chose a rather aggressive way to communicate the problem that
> debian was causing him using a nagging text

Well, we have the BTS. If the problem is really that he receives bugs that
(rightfully) he would prefer not to handle, we are already part of the
solution, not part of the problem.

More to the point, he even subscribed to his package in the BTS! For
an author who says he does not want to receive bug reports about old
release, that's remarkable.

So: Is Debian particularly causing him a problem by distributing
version 5.30 in Debian stable? I don't think so (but I could be wrong).

> Lets just find a way where our users stop pestering him and call it a day...
> 
> This happens all the time in all the projects

Well, let FSM hear you. By reading the code and his comments, I don't
think there will be a "solution" which satisfies him and our users at
the same time.

Thanks.

Acknowledgement sent to Jamil Said Jr. <jamilsaid@hotmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Mon, 04 Apr 2016 20:39:12 GMT) (full text, mbox, link).

Message #355 received at 819703@bugs.debian.org (full text, mbox, reply):

I have not looked at the code, but this approach seems to me to have the
smaller change possible and still completely solve the issue:

At some point the code will compare the date of the version with the value
that it has stored (I believe 18 months), and complain if the version is
older. Why don't just change the value store to compare from 18 months to
1800000 months or so? That way all software design is preserved and we
achieve of goal of never showing this rude, disruptive and demeaning warning
which makes no sense in a stable branch (or in any other branch, quite
frankly).

Jamil

Message #360 received at 819703@bugs.debian.org (full text, mbox, reply):

On Mon, Apr 04, 2016 at 02:33:39PM -0700, Jamil Said Jr. wrote:
> I have not looked at the code, but this approach seems to me to have the
> smaller change possible and still completely solve the issue:
> 
> At some point the code will compare the date of the version with the value
> that it has stored (I believe 18 months), and complain if the version is
> older. Why don't just change the value store to compare from 18 months to
> 1800000 months or so?

Look at the code. Even if you are not a programmer, it's easy to understand:

http://sources.debian.net/src/xscreensaver/5.30-1/driver/prefs.c/?hl=1739#L1739

Instead of "months > 18" you can just put "0", which is always false.

This would be equivalent to using an infinite amount of time in your example.

But this is not even necessary because you can just put a "return 0;"
as the very first line in the senescent_p function.

So yes, you are right that this annoying warning may be removed by
changing or adding a single line, a very small change indeed.

The "only" problem is that the author does not want anybody to do that
(read the comments at the beginning of the function).

Thanks.

Acknowledgement sent to Jamil Said Jr. <jamilsaid@hotmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Mon, 04 Apr 2016 23:36:03 GMT) (full text, mbox, link).

Message #365 received at 819703@bugs.debian.org (full text, mbox, reply):

Santiago Vila wrote:

> The "only" problem is that the author does not want anybody to do that
(read the comments at the beginning of the function).

Santiago, thank you for your response. However, I believed that we were
passed this point already, no?

The author wishes, if granted, would be "the end" of usable, nagging-free
stable branches. Can you imagine if all of your packages in a stable
installation started to (rudely) complain and harass you about your "old
version". Helloooooo, stable branches deliberately keep older versions for
better stability! Stable branches are preferable in a myriad of cases; just
look at what NASA did in 2013, they chose Debian for the ISS astronaut's
laptops and went with Debian 6 instead of the current Debian 7 at the time,
for extra stability! Should we be nagging the astronauts to update the
screensaver? See:
http://www.zdnet.com/article/to-the-space-station-and-beyond-with-linux/

The author, out of his own volition, released the code under a free, open
source license. End of story. Take this aberration (warning) out and comply
with whatever needed legally (like change the name of the program, etc). I
have no qualms with that. If the author wish was reasonable, I would be more
than glad to comply - but his wish is not reasonable.

Cheers,
Jamil

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Tue, 05 Apr 2016 03:15:04 GMT) (full text, mbox, link).

Acknowledgement sent to Eli the Bearded <debian@eli.users.panix.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 03:15:04 GMT) (full text, mbox, link).

Message #370 received at 819703@bugs.debian.org (full text, mbox, reply):

Like it or not, JWZ considers xscreensaver to be frontline system
security. If it doesn't LOCK YOUR SCREEN, it's broken. If you don't
want to track the security updates, you are (in his mind) harming users.
That is why he specifically suggests Gnome's screensaver: it's a as
hardened as a luggage lock. 

A version, today, over about five months old is going to have at least
one security hole: you can crash out of the password prompt (at least in
some cases) by hot swapping monitors at a critical time.

So:

A) Track the current version.

B) Backport all the bug fixes.

C) Fork to xluggagelock (or your name of choice for the insecure
version)

D) Stop pretending to include xscreensaver.

At least, that's how I think you'll satisfy JWZ.

Acknowledgement sent to Peter Nowee <peter@peternowee.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 03:21:04 GMT) (full text, mbox, link).

Message #375 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Mon, Apr 04, 2016 at 03:48:44PM +0000, ireulx wrote:
> When did the Free Software Community come to mean Debian users?
> When did 'needs' come to mean 'wants'?
> 
> Debian Social Contract (1997)
> -----------------------------
> We will support people who create or use both free and non-free works on Debian.
> We will be guided by the needs of our users and the free software community.
> 
> Debian Social Contract (2016)
> -----------------------------
> We will support people who use Debian.
> We will be guided by the wants of our users.
> When a creator that has been part of the free software community for decades
> makes a polite request we will tell them that they "obviously haven't understood
> how distributions work and what stable releases are" (i.e. that they need to
> conform to our way of doing things).
> We will then change their code against their wishes and call them "ignorant",
> "stubborn", "crazy" and a "dick."
> We will focus on the distribution _we_ want to use, not on the broader free
> software community.
> P.S. Our petty wants are more important than upstream's needs. 		 	   		  

I don't agree with the picture you are trying to paint here.

First, I see that many commenters here are trying to consider the 
upstream creator's interests. Several people here have come up with 
solutions that will help the author reduce the number of old bug 
reports he receives.

Second, judging by his comments here and in his code, the author was 
from the very beginning fully aware that the time-activated warnings 
were going to cause problems in the context of Debian stable. He either 
intended or did not care about that. So who is breaking the social 
contract here?

Anyway, I changed my mind a bit on what I think should be done with 
this package in Debian right now:

I still think the warnings can and should be patched out in stable / 
Jessie and I still think we should at the same time try to reduce the 
flow of bug reports to the upstream author, who has indeed been part of 
the free software movement for decades, for example by adding a Debian 
bug tracker URL near his URL/email address. I don't think we should be 
removing his email address.

However, with regard unstable/future versions of Debian, I think that 
the upstream author has shown that he is willing to go to great lengths 
to prevent the perpetual use of individual releases of his software. 
Given the problems caused by his actions so far, that it all seems to 
have been quite premeditated and that his recent comments show that he 
does not have any regrets, I fear he might take even more damaging 
action in the future if his demands are not met. In short, I do not 
trust him anymore. Removing his software from unstable ensures that he 
cannot do any more damage.

That said, I still think that making it difficult for users to 
perpetualy use an individual software release goes against both the 
letter ("permission to use") and spirit of free software. Making the 
coercion part of the software itself and referring to it as a 'feature' 
that is 'behaving as intended' does not change that. I hope the author 
can reflect on that.

Finally, could the maintainer (Tormod) please comment? Is an update in 
the works? Or would you welcome a non-maintainer upload (NMU)?

Best regards,
Peter Nowee

[signature.asc (application/pgp-signature, inline)]

Acknowledgement sent to - <hob4bit@googlemail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 05:33:03 GMT) (full text, mbox, link).

Message #380 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi, I also think the author is stubborn.

However, there is a workaround and that does not even need a patch or
update. Just set "lock: True" in "$HOME/.xscreensaver":

# XScreenSaver Preferences File
# Workaround stubborn "This version of xscreensaver is VERY OLD! Please
upgrade!" bug

timeout:    0:05:00
cycle:        0:10:00
lock:        True
lockTimeout:    0:06:00
passwdTimeout:    0:00:30
splash:        False
splashDuration:    0:00:00
fade:        False
unfade:        False

mode:           off


This disables the pop when you login. I don't know why but it works. I
found this out because some of my machines did not have this nagging.

All my systems have been updated with this workaround. Since the stubborn
author may read this and surely this loop hole will be patche dout int he
next version I have decded to abndon "xscreensaver" and switch to
"light-locker". I'll will be rolling out this fix to my systems.

Debian should remove "xscreensaver" and suggest people use "light-locker".

[Message part 2 (text/html, inline)]

Acknowledgement sent to Axel Beckert <abe@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 07:21:03 GMT) (full text, mbox, link).

Message #385 received at 819703@bugs.debian.org (full text, mbox, reply):

Hi,

Eli the Bearded wrote:
> Like it or not, JWZ considers xscreensaver to be frontline system
> security. If it doesn't LOCK YOUR SCREEN, it's broken. If you don't
> want to track the security updates, you are (in his mind) harming users.

You seem not aware that Debian _tracks_ security updates in stable.
Just not features. We backport security fixes to the current version
in stable.

See e.g.
https://packages.qa.debian.org/x/xscreensaver/news/20160112T063226Z.html
for the last security update in Jessie (i.e. the aforementioned
version) and see https://packages.qa.debian.org/x/xscreensaver.html
for the remaining security updates in oldstable and oldoldstable (no
more supported now).

> That is why he specifically suggests Gnome's screensaver: it's a as
> hardened as a luggage lock. 

And once again: GNOME Screensaver is not alternative to xscreensaver
as it lacks features and pulls in a lot of GNOME stuff which is
unwanted for other desktop environments.

> At least, that's how I think you'll satisfy JWZ.

We should satisfy our users. And their demand is obvious.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Acknowledgement sent to Sandbox Oliver-Kutschke <sandbox@oliver-kutschke.de>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 07:45:10 GMT) (full text, mbox, link).

Message #390 received at 819703@bugs.debian.org (full text, mbox, reply):

As always. Bla bla bla! Don't talk! Fix it in stable or kick it! NOW!

Acknowledgement sent to Marc Haber <mh+debian-packages@zugschlus.de>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 08:42:04 GMT) (full text, mbox, link).

Message #395 received at 819703@bugs.debian.org (full text, mbox, reply):

> Like it or not, JWZ considers xscreensaver to be frontline system
> security. If it doesn't LOCK YOUR SCREEN, it's broken. If you don't
> want to track the security updates, you are (in his mind) harming users.

If there is such a bug in xscreensaver in stable, why is the release
not tagged as critical security release, and why was the issue not
communicated more clearly, maybe even with a reproducer and a patch?

> A version, today, over about five months old is going to have at least
> one security hole: you can crash out of the password prompt (at least in
> some cases) by hot swapping monitors at a critical time.

CVE number?

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Acknowledgement sent to Daniel Shahaf <danielsh@apache.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 09:12:09 GMT) (full text, mbox, link).

Message #400 received at 819703@bugs.debian.org (full text, mbox, reply):

Marc Haber wrote on Tue, Apr 05, 2016 at 10:38:16 +0200:
> Eli the Bearded wrote:
> > A version, today, over about five months old is going to have at least
> > one security hole: you can crash out of the password prompt (at least in
> > some cases) by hot swapping monitors at a critical time.
> 
> CVE number?

I'm not Eli, but I believe he's referring to CVE-2015-8025 (#802914),
which was fixed in 5.30-1+deb8u1 that was uploaded to jessie-security on
2015-10-25.

I don't know how long the fix had been publicly available for before it
was uploaded to jessie-security.

Cheers,

Daniel

Acknowledgement sent to Hilko Bengen <bengen@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 09:39:04 GMT) (full text, mbox, link).

Message #405 received at 819703@bugs.debian.org (full text, mbox, reply):

* Daniel Shahaf:

> I'm not Eli, but I believe he's referring to CVE-2015-8025 (#802914),
> which was fixed in 5.30-1+deb8u1 that was uploaded to jessie-security on
> 2015-10-25.
>
> I don't know how long the fix had been publicly available for before it
> was uploaded to jessie-security.

Since there is no public VCS, all we can go by is the date stamp from
xscreensaver-5.34/utils/version.h: 24-Oct-2015.

Cheers,
-Hilko

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Tue, 05 Apr 2016 16:09:04 GMT) (full text, mbox, link).

Acknowledgement sent to "A.B." <opensource@ajb.ddns.us>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 16:09:04 GMT) (full text, mbox, link).

Message #410 received at 819703@bugs.debian.org (full text, mbox, reply):

On Tue, 5 Apr 2016 05:16:51 +0200 Peter Nowee <peter@peternowee.com> wrote:

> Second, judging by his comments here and in his code, the author was
> from the very beginning fully aware that the time-activated warnings
> were going to cause problems in the context of Debian stable. He either
> intended or did not care about that.

Yes.

Please, everyone, stop acting like upstream is acting in good faith 
here. He's smart, he knows how Debian and Linux distributions work, and 
he is _choosing_ to throw a tantrum that would embarrass a small child.

He deliberately created a situation where this was bound to happen and 
where it is impossible to meet his demands. There are only a few courses 
of action for Debian here, which have been discussed at length. That's 
fine, but please let's stop trying to figure out how to please upstream. 
You can't, because it is impossible by design to do so.

Acknowledgement sent to Sharuzzaman Ahmat Raslan <sharuzzaman@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 17:09:13 GMT) (full text, mbox, link).

Message #415 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi all,

I would like to suggest that the source code of all version of xscreensaver
to be forked and maintained in Alioth. The software name should be change
also. Maybe debian-screensaver is a good choice of name.

All email address or URL of upstream should be removed from the forked
source code. Only the name of the upstream should be maintained to show the
origin of the code.

From the forked code, Debian should be free to patch out all the line
causing the issues in this bug report.

Upstream should not have any interest on the forked code as he is not the
one that are going to maintain or responding to bug report.

Thanks.

-- 
Sharuzzaman Ahmat Raslan

[Message part 2 (text/html, inline)]

Acknowledgement sent to Steven Chamberlain <steven@pyro.eu.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 17:51:09 GMT) (full text, mbox, link).

Message #420 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi,

I suggest this bug,
#819703 - xscreensaver: please disable "This version of XScreenSaver is very old! Please upgrade!" message
only be used to discuss that issue and how to fix it in stable.

To anyone else waiting for that to be fixed in the package, please be
patient for the maintainer to respond about the patch in
https://bugs.debian.org/819703#5, or otherwise for someone else to
do an NMU.

I've filed a separate bug,
#820105 - xscreensaver: please consider removal from sid
regarding the upstream maintainer's request for Debian to stop
distributing xscreensaver, and other concerns about carrying it in
future Debian stable releases.

And there already was a bug,
#802914 - xscreensaver: CVE-2015-8025: crash when hot-swapping monitors while locked
where that security issue was discussed, and backported to Debian
squeeze-lts, wheezy and jessie a long time ago.

Thanks,
Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#819703; Package xscreensaver. (Tue, 05 Apr 2016 18:33:09 GMT) (full text, mbox, link).

Acknowledgement sent to Tormod Volden <debian.tormod@gmail.com>:
Extra info received and forwarded to list. (Tue, 05 Apr 2016 18:33:10 GMT) (full text, mbox, link).

Message #425 received at 819703@bugs.debian.org (full text, mbox, reply):

Thanks to Michael (and others?) for providing patches, generally the
most valuable contribution in a bug report.

Jamie, you could have deleted all e-mail reports from Debian users in
the time it took you to write this Easter egg :)

(Just responding to the productive participants first, since this may get long)

Please calm down people, a little pop-up and an extra click is
annoying but it is not the end of the world. The pop-up message may be
direct, but is it not attacking any minorities, genders or sexual
preferences. There is no need for name calling and disrespectful talk
here. Especially the Debian contributors around should know there is a
code of conduct that should be followed here in bug reports as in any
other Debian activity. If you are not contributing, but are here to
whine or me-too, your presence is not needed or helpful, so please go
back to fecebook/riddit. Also know that any changes to the stable
distribution is a long and difficult process, so patience is needed by
all parties.

There is often a lack of respect, consideration and gratitude towards
the upstream author of software. Creating the software and generating
original content is the hardest and most meritable part. It seems some
people feel entitled just because they are repackaging software or
even are being able to install it. Jamie has done a phenomenal job of
creating and improving XScreenSaver, and gives it away for free to us
to use and modify as we want, what more can one ask for? He is also an
exemplary upstream in that he follows the xscreensaver bug tracker in
Debian, and often comments on bug reports. We are grateful for this
and wishes more upstreams would do the same. Granted, the bug
reporters don't always get to hear what they wanted :) but overall it
is a privilege to have direct communication with the original software
creator.

It is understandable that upstreams are frustrated by seeing users
stuck with older versions. It is sometimes frustrating for the
packagers too, and the users. However it is the way a stable
distribution works. The concept of stable releases is not unknown to
the Jamie either, in fact he gives no access to any development
repository or snapshots of XScreenSaver, and sometimes takes long
between his releases. Version 5.30, which he hates us for having in
stable, was still the latest release but already almost a year old
when we entered the freeze at that time. If you look at the upstream
changelog, the changes since then up to 5.34 are minor, and heavily
focused on iOS issues that are not of interest to our users. It can be
added that the one security issue that came up last year, was fixed
immediately in squeeze and sid when we were notified. So the "old"
version in stable is not a big issue, but a small irritation for every
little fix that upstream has added later.

Now it is clear for everybody that we don't want software to suddenly
change by itself in a stable distribution. As stable distribution
users we want our software to work as it did yesterday unless we
explicitly request changes. The introduction of the present Easter egg
was an awkward gesture by the author and an oversight from our side to
let it slip in. This is a small technical issue that we can solve
easily. The author wants to make a point about our distribution of
older versions, and this is indeed a general question that should be
discussed. This is of strategical importance, but does not belong here
in this bug report.

Debian users should always report bugs to Debian and not directly
upstream. So the author being spammed by Debian users on old versions
should in principle not happen. If the current software encourages
people to send bug reports to the author we will look into and fix
this.

It is possible that I have not read all 400 comments here, but I think
I have got enough information to work on the problem. It is good to
see so many care for, and use, xscreensaver. Usually this is a quiet
place. Thanks, all.

Tormod

Acknowledgement sent to alberto fuentes <pajaro@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 19:27:10 GMT) (full text, mbox, link).

Message #430 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Tue, Apr 5, 2016 at 8:31 PM, Tormod Volden <debian.tormod@gmail.com>
wrote:

> Thanks to Michael (and others?) for providing patches, generally the
> most valuable contribution in a bug report.
>

Thanks for being a calm and sensible maintainer amidst the turmoil!

[Message part 2 (text/html, inline)]

Added tag(s) pending. Request was from Axel Beckert <abe@debian.org> to control@bugs.debian.org. (Tue, 05 Apr 2016 21:21:10 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Tue, 05 Apr 2016 23:03:07 GMT) (full text, mbox, link).

Message #437 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Tue, Apr 05, 2016 at 08:31:46PM +0200, Tormod Volden wrote:
> Debian users should always report bugs to Debian and not directly
> upstream. So the author being spammed by Debian users on old versions
> should in principle not happen. If the current software encourages
> people to send bug reports to the author we will look into and fix
> this.

Thanks for your reply.

Here is a patch I was working on to add links to the Debian BTS in the 
several places where bug reporting is encouraged (man pages, dialog 
boxes). Perhaps it can be of use. Note that I did not have a chance to 
test the change I made to the Motif dialog box (driver/demo-Xm.c) yet.

Good luck, thanks,
Peter Nowee

[60_bugs_to_debian_bts.patch (text/x-diff, attachment)]

[signature.asc (application/pgp-signature, inline)]

Acknowledgement sent to Jamil Said Jr. <jamilsaid@hotmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 23:21:04 GMT) (full text, mbox, link).

Message #442 received at 819703@bugs.debian.org (full text, mbox, reply):

I have a question and would appreciate if someone can point me to the right
direction.

I would like to fix this warning on my own. I code in bash and other
languages. My difficulty here is that I cannot find the offending code
anywhere on my installations.

I know that grep and sed can work on binary files... but where's this code?
I looked all over the place and could not find it.

What am I missing here? Any help is very appreciated.

Cheers,
Jamil

Reply sent to Tormod Volden <debian.tormod@gmail.com>:
You have taken responsibility. (Tue, 05 Apr 2016 23:36:16 GMT) (full text, mbox, link).

Notification sent to Daniel Shahaf <danielsh@apache.org>:
Bug acknowledged by developer. (Tue, 05 Apr 2016 23:36:16 GMT) (full text, mbox, link).

Message #447 received at 819703-close@bugs.debian.org (full text, mbox, reply):

Source: xscreensaver
Source-Version: 5.34-2

We believe that the bug you reported is fixed in the latest version of
xscreensaver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 819703@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tormod Volden <debian.tormod@gmail.com> (supplier of updated xscreensaver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 05 Apr 2016 22:53:13 +0200
Source: xscreensaver
Binary: xscreensaver xscreensaver-data xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra xscreensaver-screensaver-webcollage xscreensaver-screensaver-bsod
Architecture: source amd64
Version: 5.34-2
Distribution: unstable
Urgency: medium
Maintainer: Tormod Volden <debian.tormod@gmail.com>
Changed-By: Tormod Volden <debian.tormod@gmail.com>
Description:
 xscreensaver - Screensaver daemon and frontend for X11
 xscreensaver-data - Screen saver modules for screensaver frontends
 xscreensaver-data-extra - Extra screen saver modules for screensaver frontends
 xscreensaver-gl - GL(Mesa) screen saver modules for screensaver frontends
 xscreensaver-gl-extra - Extra GL(Mesa) screen saver modules for screensaver frontends
 xscreensaver-screensaver-bsod - BSOD screen saver module from XScreenSaver
 xscreensaver-screensaver-webcollage - Webcollage screen saver module from XScreenSaver
Closes: 819595 819703
Changes:
 xscreensaver (5.34-2) unstable; urgency=medium
 .
   * Fix sort order in hacks/Makefile (for reproducible builds)
     (Closes: #819595)
   * Disable Easter egg about "outdated" version
     (Closes: #819703)
Checksums-Sha1:
 3e0b09dedd3ac52ca6c0925198b89b47590cdd31 2738 xscreensaver_5.34-2.dsc
 9d92fc91deab8cd85f18506e3e5db0dea9c3100d 80024 xscreensaver_5.34-2.diff.gz
 9f18686ff1f681806ddee3cc88bea12ac75fd2ff 1412832 xscreensaver-data-dbgsym_5.34-2_amd64.deb
 10dc9fdf3827ed144b0a2ac63e819158dfb0d2d6 6332312 xscreensaver-data-extra-dbgsym_5.34-2_amd64.deb
 7d0a3afe0a52ebdcaebac4642891aafcd2ce796f 1035028 xscreensaver-data-extra_5.34-2_amd64.deb
 667ae740527fbe33788b8a0dd12e7d3553874b7f 312688 xscreensaver-data_5.34-2_amd64.deb
 f421c8db672fe36353874b7a9d08eef29dbca6b7 444322 xscreensaver-dbgsym_5.34-2_amd64.deb
 9f1294d286a0bc3b134c2c779019b05c3610d83e 6932468 xscreensaver-gl-dbgsym_5.34-2_amd64.deb
 96d27b3b7b38267e9986571813308bb4e9e68a6d 5355664 xscreensaver-gl-extra-dbgsym_5.34-2_amd64.deb
 e0551d0a05177ae32eae7749ecb2448c629a03ae 1874314 xscreensaver-gl-extra_5.34-2_amd64.deb
 d1751371af5e8766c8716c47be1873b2b4af3caf 1197098 xscreensaver-gl_5.34-2_amd64.deb
 cb9726a91b1d4c9c385c3837d6e4a20a6cf42276 162324 xscreensaver-screensaver-bsod-dbgsym_5.34-2_amd64.deb
 05ea563903a713c4ce012a926326c66f336f6a56 165626 xscreensaver-screensaver-bsod_5.34-2_amd64.deb
 605acd79ff57083ce76454c2c4ec8a8b60cd1584 14336 xscreensaver-screensaver-webcollage-dbgsym_5.34-2_amd64.deb
 3ee3b0ca382f6b4725dd12f199ca02fa561f77ab 63268 xscreensaver-screensaver-webcollage_5.34-2_amd64.deb
 1fd07d79814d74bccb99db3628117b5081d238e1 561296 xscreensaver_5.34-2_amd64.deb
Checksums-Sha256:
 bb60e9f18c856655eb5a15423a07f6ef46df6dc7ecd2da155b1cdb67ed772474 2738 xscreensaver_5.34-2.dsc
 03b8483c764ee8687c2fceb31f9d7d7c9987fd14de584974fbeda0883d4a2f85 80024 xscreensaver_5.34-2.diff.gz
 67c84400b41bbdfde9f8b5da97ed0cc7d162e47f5f6d88913912cada07aebb13 1412832 xscreensaver-data-dbgsym_5.34-2_amd64.deb
 ee370bd696bd23bc8eb0a8bfed0e50235df03731a70ba9fea1dfbf7a0d7fe826 6332312 xscreensaver-data-extra-dbgsym_5.34-2_amd64.deb
 9884b22f49757e2618c3183d89679d2844c12eddb7ede21ed0ea60ed1a4b4d4a 1035028 xscreensaver-data-extra_5.34-2_amd64.deb
 6f517d51d843f612ebaa7abf52d96cf0f1959f815e7ee835ba063f9a3329969e 312688 xscreensaver-data_5.34-2_amd64.deb
 87f100b3540d2d366712e4a2366b13083963ff4b9bfb2a3a462b0fa928fd6f56 444322 xscreensaver-dbgsym_5.34-2_amd64.deb
 046365a61ad324bc4de70420ba8a590c748d07a413e3d4a23d25df4177babbc7 6932468 xscreensaver-gl-dbgsym_5.34-2_amd64.deb
 e50fa3a43a2cd307f89e4786224c7bef315fd8efa6ae314b6183e0db36b4c9cc 5355664 xscreensaver-gl-extra-dbgsym_5.34-2_amd64.deb
 431e8f6f0d9dd65726c3a4350e5a4a29a4bbe379641bf37b1591a375870381ea 1874314 xscreensaver-gl-extra_5.34-2_amd64.deb
 12c2cc580156e0fb2a7bf8508697d6987cfc422ed6cd86e85b54adc8fbd978a9 1197098 xscreensaver-gl_5.34-2_amd64.deb
 8a63f2c42f419d3a70030f8585398d4c716af82b2706d93d46e06937cb0ebdd2 162324 xscreensaver-screensaver-bsod-dbgsym_5.34-2_amd64.deb
 d90ca72c0b6a29d5b8eee8fc4e6cf9df29dfc2f6c5f7f5f72ffc1714132a044e 165626 xscreensaver-screensaver-bsod_5.34-2_amd64.deb
 a2926be366beee956fe13ce359cf721f119241e6055e69f676dd6e50f65b6fb5 14336 xscreensaver-screensaver-webcollage-dbgsym_5.34-2_amd64.deb
 28b879d04afb649ce39bf185922e270981e1020703d961a1780168fb717ab32f 63268 xscreensaver-screensaver-webcollage_5.34-2_amd64.deb
 594fa0cd454ea91adb3487de319c19d2557660eaed9284b76d47b64b21e1c107 561296 xscreensaver_5.34-2_amd64.deb
Files:
 5f9e0012a6e86c5c90f31a455aaca2c7 2738 x11 optional xscreensaver_5.34-2.dsc
 21827462d16a17d92242f4a3df4d3212 80024 x11 optional xscreensaver_5.34-2.diff.gz
 186f32c4e88007fc0f927ca9744cebdf 1412832 debug extra xscreensaver-data-dbgsym_5.34-2_amd64.deb
 b8dab82d4525db5cea1acf6d34305001 6332312 debug extra xscreensaver-data-extra-dbgsym_5.34-2_amd64.deb
 837216888c44c8ab2bfa2613c9d1d443 1035028 x11 optional xscreensaver-data-extra_5.34-2_amd64.deb
 a6e3ff97e29a55b0bb62b110f2758a6c 312688 x11 optional xscreensaver-data_5.34-2_amd64.deb
 629542ffa8d57830226b0468d3098489 444322 debug extra xscreensaver-dbgsym_5.34-2_amd64.deb
 5fd68cce3f306d4f31dbadbe0bd00470 6932468 debug extra xscreensaver-gl-dbgsym_5.34-2_amd64.deb
 3ddb60a1886328439f7fcc0aa6c096e8 5355664 debug extra xscreensaver-gl-extra-dbgsym_5.34-2_amd64.deb
 597706ee7973400aa0a9a80df6511ff1 1874314 x11 optional xscreensaver-gl-extra_5.34-2_amd64.deb
 732723c755a66ed38fb5ce796dd0e743 1197098 x11 optional xscreensaver-gl_5.34-2_amd64.deb
 e26edab4bdba862f9e32865455204a27 162324 debug extra xscreensaver-screensaver-bsod-dbgsym_5.34-2_amd64.deb
 34cdd3e9e0af42d8757e03ee339501cb 165626 x11 optional xscreensaver-screensaver-bsod_5.34-2_amd64.deb
 2cc25ad5550e6374ed72d0268ac167ea 14336 debug extra xscreensaver-screensaver-webcollage-dbgsym_5.34-2_amd64.deb
 5c7cfaf6cd01a91f4914b4d5dbf06a50 63268 x11 optional xscreensaver-screensaver-webcollage_5.34-2_amd64.deb
 93dd48b0401ff02804cd22997c36b219 561296 x11 optional xscreensaver_5.34-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXBEYQAAoJEGvmY8daNcl17ucP/jE9rZ8n/WVv6CiP7yDBrcYt
IgbLxw7BcOb3FaonqFEFA/xbXqJHrrgehBN1i736deBWN/xdDM6cRVjqGkdJLtPJ
Fx+/AyS3DPHL/o1CWO7I5ambubz5Ocz+5b/89bhA3YsjKEv1npuFDk1WIw8nEGqq
igxW1cdHlJ86FhMPoeTrxnpU/1LyjTRtv3tHKoldlO9/KcNrN+rUd7Hus8Qh9pao
AriVYG+wvvGSeiIGTTDCrjXupfUurUQYz5rkQrU/AnqTsMRGTfpN7Bn7ApBT4O2G
jWzcqfy7QmVXUKM7x+Rdasq5wLDhlY5BqWszHS60EW71Ebp7nU1FsSQz3MK2Ymjs
DJmMiWIsA9b2MwbOj1ma8NVVH4iKf3Qp4TOL6pN+AKX2YEQMWk3LaTde+/nzhWy2
5VNzEDnYWIWZmnEzZQRt8oXsmRyqN259HAS04oSxoqjz9u+UA2zSJyXKa3/WFE4b
RB1q1f7W5/4Kg9X2BYXTcaP2t94omHLoWgYLyCWLY9rhZX1VekpbGi7msvJTnMIl
GwFaM3UHQ4efghceI9uBZR4UBSCmOSzLpY2k3RZXHX9ZfbiyT9s1uPbiGWpp1tGp
K267l8MEZ0yGGyQUWXT7nos+2YBn7EPIL1f8z5yGrBozGQYSj2FlN/Y8F/1QZdam
qqnAWuQKGpI5StnBN7Yk
=YOEp
-----END PGP SIGNATURE-----

Acknowledgement sent to Santiago Vila <sanvila@unex.es>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 05 Apr 2016 23:39:03 GMT) (full text, mbox, link).

Message #452 received at 819703@bugs.debian.org (full text, mbox, reply):

On Wed, Apr 06, 2016 at 04:18:17PM -0700, Jamil Said Jr. wrote:
> I have a question and would appreciate if someone can point me to the right
> direction.
> 
> I would like to fix this warning on my own. I code in bash and other
> languages. My difficulty here is that I cannot find the offending code
> anywhere on my installations.
> 
> I know that grep and sed can work on binary files... but where's this code?
> I looked all over the place and could not find it.

The source code is not "installed" by default.

If you have a suitable deb-src line in /etc/apt/sources.list, try

apt-get source xscreensaver

After that, the steps to build a package from source are the same
regardless of the package you want to build, i.e. it's not specific to
xscreensaver, and it's widely documented.

Thanks.

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Wed, 06 Apr 2016 03:51:03 GMT) (full text, mbox, link).

Acknowledgement sent to Jamil Said Jr. <jamilsaid@hotmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Wed, 06 Apr 2016 03:51:04 GMT) (full text, mbox, link).

Message #457 received at 819703@bugs.debian.org (full text, mbox, reply):

Dear Tormod,

I read your email and my understanding is that only the unstable version
5.34 and beyond will be fixed? What about the stable version 5.30? Can you
also fix that?

I would be very disappointed if the stable version is not fixed. I work a
lot with people with low computer skills, most of which are also in the
lower income brackets. Many depend on Debian stable on a day by day basis. I
spent an innumerable amount of hours educating people about stable branches,
and how to update via a conservative apt-get update. Those people will stay
with their computers for a large number of years, and they don't have a clue
about backports. 

I think it would be a very bad decision to leave people being pestered for
years by this rude, disruptive and disingenuous warning. Yes, it is
disingenuous, because it says "If this is the latest version that your
distro ships, then your distro is doing you a disservice." - this statement
is false, because using old versions (stable branches) have pros and cons,
and may be ideal to many people and situations (I almost always use and
recommend stable, and in 2013 NASA chose stable of Debian 6 instead of
stable Debian 7 for the ISS astronaut's laptops, tell me about using older
versions for stability). Also, this warning unjustly denigrates Debian and
will confuse and scare many.

I thus ask you to reconsider and fix this issue on the stable version as
well. It could be done as a security fix, perhaps? The rationale is that the
warning is disingenuous and contains inaccurate information (i.e.: that
using older versions is a disservice). Please don't let this thing hanging
out there, I know that many people will have to deal with this annoyance for
years, and that really undermines the trust and goodwill that this people
have on Debian (and Linux in general). 

I hope you will reconsider, in case there are no plans to fix stable.

Respectfully,
Jamil Said

PS: Santiago, gracias amigo! I will look into the info you provided me.

Acknowledgement sent to Marc Haber <mh+debian-packages@zugschlus.de>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Wed, 06 Apr 2016 05:54:05 GMT) (full text, mbox, link).

Message #462 received at 819703@bugs.debian.org (full text, mbox, reply):

On Wed, Apr 06, 2016 at 01:04:59AM +0800, Sharuzzaman Ahmat Raslan wrote:
> Maybe debian-screensaver is a good choice of name.

I disagree. That would suggest that we endorse this and consider this
the canonical screensaver to use in Debian, while the opposite is
actually the case.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Acknowledgement sent to Adam Borowski <kilobyte@angband.pl>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Wed, 06 Apr 2016 06:18:04 GMT) (full text, mbox, link).

Message #467 received at 819703@bugs.debian.org (full text, mbox, reply):

On Wed, Apr 06, 2016 at 08:43:42PM -0700, Jamil Said Jr. wrote:
> I read your email and my understanding is that only the unstable version
> 5.34 and beyond will be fixed? What about the stable version 5.30? Can you
> also fix that?

Updates to stable that are not security issues take quite a long time to be
released, so even if Tormod uploaded to stable-proposed-updates today you
wouldn't see it anytime soon.  There's volatile aka jessie-updates but not
everyone has that enabled...

If you need an unofficial fix right now, you can grab packages for jessie
with the one-line patch applied from:
    https://angband.pl/debian/pool/main/x/xscreensaver/
(built for amd64 i386 x32 armhf, holler if you need more)

-- 
A tit a day keeps the vet away.

Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#819703; Package xscreensaver. (Wed, 06 Apr 2016 07:48:19 GMT) (full text, mbox, link).

Acknowledgement sent to Tormod Volden <debian.tormod@gmail.com>:
Extra info received and forwarded to list. (Wed, 06 Apr 2016 07:48:19 GMT) (full text, mbox, link).

Message #472 received at 819703@bugs.debian.org (full text, mbox, reply):

On Thu, Apr 7, 2016 at 5:43 AM, Jamil Said Jr. wrote:
> I read your email and my understanding is that only the unstable version
> 5.34 and beyond will be fixed? What about the stable version 5.30? Can you
> also fix that?

Hi Jamil,

Thanks for your interest in the Debian development process! Any
changes in stable must "bake" in unstable first. So in this case,
although it is not urgent in unstable, but rather in stable, it still
has to go through unstable first. The following link explains more:
https://www.debian.org/releases/proposed-updates

There are also IRC channels where you can ask questions about Debian
development without getting your hand bitten off. I don't frequent
them so I cannot give you the link off-hand. The entry to Debian
development is low and there are many ways you can start helping out.
I'd suggest looking through  https://www.debian.org/devel/join/  and
https://wiki.debian.org/Community  and
https://wiki.debian.org/DebianDevelopment . Don't get scared by all
the bureaucracy and formalities described, you can do a lot also
without all the rubber stamps.

Regards,
Tormod

Acknowledgement sent to Axel Beckert <abe@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Wed, 06 Apr 2016 07:48:22 GMT) (full text, mbox, link).

Message #477 received at 819703@bugs.debian.org (full text, mbox, reply):

Dear Jamil,

Jamil Said Jr. wrote:
> I read your email and my understanding is that only the unstable version
> 5.34 and beyond will be fixed? What about the stable version 5.30?

That's next.

If bugs are not security issues, they always should be fixed first in
unstable, bascially as a proof that the fix works. The Stable Release
Managers usually won't accept uploads to stable-proposed-updates or
stable-updates, if the accordings bugs are not already fixed in
unstable.

It's a little bit more difficult in this case as the bug is still
dormant on unstable. But the code for it is definitely there and so
there's something to fix there, too.

Actually Tormod wanted to fix stable first as the issue is more
"urgent" there and I (as the one who was asked to sign/sponsor the
upload) insisted on fixing it in unstable first.

You can verify that the fix works on unstable (where the message is
not yet triggered if the time in you computer is correct) by comparing
the behaviour of 5.34-1 and 5.34-2 with the following command:

  faketime -f "+2y" xscreensaver-command -prefs

With 5.34-1 you get an additional popup, with 5.34-2 you no more get
it.

The faketime command is part of the faketime package, so you might
need to install that first.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Wed, 06 Apr 2016 19:36:03 GMT) (full text, mbox, link).

Acknowledgement sent to Jamil Said Jr. <jamilsaid@hotmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Wed, 06 Apr 2016 19:36:03 GMT) (full text, mbox, link).

Message #482 received at 819703@bugs.debian.org (full text, mbox, reply):

Dear Adam, Tormod and Axel, thank you for your answers.

Tormod said:
>> Any changes in stable must "bake" in unstable first.

Of course! I forgot about that. I love the commitment in Debian to create
the most stable OS possible. Even if it is a line of code change, should
"bake" on unstable first. I'd have chosen the same path.

Then, I am happy that this issue is following the course of being fixed and
eventually will be fixed on stable. 

Thanks for the links, I will visit them in the future.

Cheers,
Jamil

Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#819703; Package xscreensaver. (Thu, 07 Apr 2016 19:33:03 GMT) (full text, mbox, link).

Acknowledgement sent to Tormod Volden <debian.tormod@gmail.com>:
Extra info received and forwarded to list. (Thu, 07 Apr 2016 19:33:03 GMT) (full text, mbox, link).

Message #487 received at 819703@bugs.debian.org (full text, mbox, reply):

On Wed, Apr 6, 2016 at 1:01 AM, Peter Nowee <peter@peternowee.com> wrote:
> Here is a patch I was working on to add links to the Debian BTS in the
> several places where bug reporting is encouraged (man pages, dialog
> boxes). Perhaps it can be of use. Note that I did not have a chance to
> test the change I made to the Motif dialog box (driver/demo-Xm.c) yet.
>
> Good luck, thanks,
> Peter Nowee

Thanks for the patch, Peter! I have opened bug #820378 for this task.

Tormod

Merged 819703 820880 Request was from Salvatore Bonaccorso <carnil@debian.org> to control@bugs.debian.org. (Wed, 13 Apr 2016 10:45:19 GMT) (full text, mbox, link).

Reply sent to Tormod Volden <debian.tormod@gmail.com>:
You have taken responsibility. (Sat, 16 Apr 2016 21:51:19 GMT) (full text, mbox, link).

Notification sent to Daniel Shahaf <danielsh@apache.org>:
Bug acknowledged by developer. (Sat, 16 Apr 2016 21:51:19 GMT) (full text, mbox, link).

Message #494 received at 819703-close@bugs.debian.org (full text, mbox, reply):

Source: xscreensaver
Source-Version: 5.30-1+deb8u2

We believe that the bug you reported is fixed in the latest version of
xscreensaver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 819703@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tormod Volden <debian.tormod@gmail.com> (supplier of updated xscreensaver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 05 Apr 2016 21:55:42 +0200
Source: xscreensaver
Binary: xscreensaver xscreensaver-data xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra xscreensaver-screensaver-webcollage xscreensaver-screensaver-bsod
Architecture: source amd64
Version: 5.30-1+deb8u2
Distribution: jessie
Urgency: medium
Maintainer: Tormod Volden <debian.tormod@gmail.com>
Changed-By: Tormod Volden <debian.tormod@gmail.com>
Description:
 xscreensaver - Screensaver daemon and frontend for X11
 xscreensaver-data - Screen saver modules for screensaver frontends
 xscreensaver-data-extra - Extra screen saver modules for screensaver frontends
 xscreensaver-gl - GL(Mesa) screen saver modules for screensaver frontends
 xscreensaver-gl-extra - Extra GL(Mesa) screen saver modules for screensaver frontends
 xscreensaver-screensaver-bsod - BSOD screen saver module from XScreenSaver
 xscreensaver-screensaver-webcollage - Webcollage screen saver module from XScreenSaver
Closes: 819703
Changes:
 xscreensaver (5.30-1+deb8u2) jessie; urgency=medium
 .
   * Disable Easter egg about "outdated" version (closes: #819703)
Checksums-Sha1:
 f7cec9c3f2000f0447e6e6b6bf6ed10fea5eb6a2 2763 xscreensaver_5.30-1+deb8u2.dsc
 2e9c7e38d32be435e4fe86b031118a3ea3be2e10 79994 xscreensaver_5.30-1+deb8u2.diff.gz
 a2e0fe14ec65de95ea2c37ead41faccc32859c75 560564 xscreensaver_5.30-1+deb8u2_amd64.deb
 9b05d742ee5ab11968c83516ade7ae32468415d9 299830 xscreensaver-data_5.30-1+deb8u2_amd64.deb
 de3d29833acfe22f1cb22ccdaaee14e7a9559bca 1010724 xscreensaver-data-extra_5.30-1+deb8u2_amd64.deb
 3cffc963c8cf0f4bfdd462d375bfbdca25f310c7 1061654 xscreensaver-gl_5.30-1+deb8u2_amd64.deb
 b59f63689c83ee2570523b7cd284a6e4c7099b85 1623976 xscreensaver-gl-extra_5.30-1+deb8u2_amd64.deb
 474f24f7e14fba9dfdf1dd66349787f6c89a0503 61676 xscreensaver-screensaver-webcollage_5.30-1+deb8u2_amd64.deb
 b8f4d94365aa1c8ad8e59c572afe86b252643a7e 163038 xscreensaver-screensaver-bsod_5.30-1+deb8u2_amd64.deb
Checksums-Sha256:
 dc2d04da56708736df246df3fd6bafd81c40721f5fd605c2b0ed52333009bad3 2763 xscreensaver_5.30-1+deb8u2.dsc
 72d54fba16c8f4bd6fb002fbfa4a23165891f337512a362cf69c05f31e5dd028 79994 xscreensaver_5.30-1+deb8u2.diff.gz
 3840a3aeace26df7caef1e3ee71e76a069c7060e4d319718d76c9d6507ebd8ae 560564 xscreensaver_5.30-1+deb8u2_amd64.deb
 4b1f6d9013ddca309e92efa1638da819a15ba1e3e7e9be9907f8beb66348d243 299830 xscreensaver-data_5.30-1+deb8u2_amd64.deb
 d936ac341fd4096a0d64c79743ec5840c59d4c2537d6feb419d332d326da7fc1 1010724 xscreensaver-data-extra_5.30-1+deb8u2_amd64.deb
 8b3025b0b8df89749ae3c67d358ad3d14c46aec0e7a53edc353be53836415bf4 1061654 xscreensaver-gl_5.30-1+deb8u2_amd64.deb
 63c016840baca7f60d8800415b543b97b482c0b09b4ac3cbaab68ab336425c68 1623976 xscreensaver-gl-extra_5.30-1+deb8u2_amd64.deb
 2b2a6d720030f0c209b2ed428d93101d03eb17b6e39a089f7c51f9e6d280d819 61676 xscreensaver-screensaver-webcollage_5.30-1+deb8u2_amd64.deb
 124801ad8dc1098a239b7748d50bd6ecf8531c2e7736acabaa92579f2a0cd3d5 163038 xscreensaver-screensaver-bsod_5.30-1+deb8u2_amd64.deb
Files:
 52bb9cabff353195bad2ab8860131e04 2763 x11 optional xscreensaver_5.30-1+deb8u2.dsc
 e31813358bedce942eb8d05d56166d14 79994 x11 optional xscreensaver_5.30-1+deb8u2.diff.gz
 15d4bdf8e74e83a1d1c914eb1396d18d 560564 x11 optional xscreensaver_5.30-1+deb8u2_amd64.deb
 32bf8f596643ace92eaafaf25cddb954 299830 x11 optional xscreensaver-data_5.30-1+deb8u2_amd64.deb
 1aa4754144606ab581d3a123ddb74730 1010724 x11 optional xscreensaver-data-extra_5.30-1+deb8u2_amd64.deb
 5841febe678dc0f62e2ac2896668f0fe 1061654 x11 optional xscreensaver-gl_5.30-1+deb8u2_amd64.deb
 5806273a77c3d2ebfe8adad34ce97490 1623976 x11 optional xscreensaver-gl-extra_5.30-1+deb8u2_amd64.deb
 5942e02665d5bedf2b7ec4e98abdd6cb 61676 x11 optional xscreensaver-screensaver-webcollage_5.30-1+deb8u2_amd64.deb
 9ffba8eed7b8c32ac3dd7a82e53f7b89 163038 x11 optional xscreensaver-screensaver-bsod_5.30-1+deb8u2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXEDrjAAoJEC/5zVlhJha1ehQQAIYb7+6iqKbB13CNuw+jpo2c
riElvVAUDeXWgS5PsvrY8IFpSAz6u0wiIXfDseII2qoCITKdP+ay9cqoT/RllImM
DkWHjkLKGVtlOaNuP6/3ADrTyEpxlgMxcHnQRE6zwr9aX9MPzTorDWu4x2GxrYRW
kb/vBsRjq3pVhZrTSmBoNIrMKqCldbQEa08vf2+lg5FcFhG2SSgX25LjrRaamJST
FPuJBrKaZIIi/R47SuwqNJyY87XLK3IU3N2Kmi2zyL+Mg6DoKwhcNPvkydd0dLhG
3LjKFII+kRyov02hMg1jte9Vhse6rQSPGinXSFcVkcH2jczHrZd9Ab3kE5Q2eRlT
LhdZfOrRhG5HlpN/M3JdCQbPLCfcTYYgrsmc9BnwHeyd6/UKut5ZCeo6FYYpuQs7
M/C+Inl03WSeAyu2JrpxRRiuBq4NOjA6oqS1AmLKm7HQnCTu+NIN7j4kPRjhYp7x
yYHYIYkJlZUDP3f5JOQQxCQcnXyA9wr8jXmyMNmbhgvvi0eVmgqNsJew7UjzBwQk
q8WuJh28t2GoZ9yxanr6D98M+/GiCMpw3tSnxuSg+a/BE8T6FdnZKn2hf7sLgMAE
z8EmJ55UXOXwj3uZZaIPIHCJKTER9LPYr6fswmE8Kc9CJbIJ3UkYs4cyuA93RTlS
DFslMOlb/mGdPHUnaSAH
=8hVm
-----END PGP SIGNATURE-----

Reply sent to Tormod Volden <debian.tormod@gmail.com>:
You have taken responsibility. (Sat, 16 Apr 2016 21:51:20 GMT) (full text, mbox, link).

Notification sent to treaki <treaki@treaki.tk>:
Bug acknowledged by developer. (Sat, 16 Apr 2016 21:51:20 GMT) (full text, mbox, link).

Reply sent to schwinn <al.schwinn@gsi.de>:
You have taken responsibility. (Mon, 18 Apr 2016 13:36:05 GMT) (full text, mbox, link).

Notification sent to Daniel Shahaf <danielsh@apache.org>:
Bug acknowledged by developer. (Mon, 18 Apr 2016 13:36:05 GMT) (full text, mbox, link).

Message #503 received at 819703-done@bugs.debian.org (full text, mbox, reply):

Package: xscreensaver
Version: 5.30-1+deb8u2

--- Please enter the report below this line. ---

- closed - already fixed in 5.30-1+deb8u2  (Hope subject generated from 
reportbug-ng is sufficient to close a bug)

Reply sent to schwinn <al.schwinn@gsi.de>:
You have taken responsibility. (Mon, 18 Apr 2016 13:36:06 GMT) (full text, mbox, link).

Notification sent to treaki <treaki@treaki.tk>:
Bug acknowledged by developer. (Mon, 18 Apr 2016 13:36:06 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Tue, 19 Apr 2016 07:03:05 GMT) (full text, mbox, link).

Acknowledgement sent to Harald Hellmuth <harald.hellmuth@unitybox.de>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 19 Apr 2016 07:03:05 GMT) (full text, mbox, link).

Message #512 received at 819703@bugs.debian.org (full text, mbox, reply):

On Sat, 16 Apr 2016 21:47:59 +0000 Tormod Volden <debian.tormod@gmail.com> wrote:

Hi Tormod,


> Source: xscreensaver
> Source-Version: 5.30-1+deb8u2
> 
> We believe that the bug you reported is fixed in the latest version of
> xscreensaver, which is due to be installed in the Debian FTP archive.
> 
> A summary of the changes between this version and the previous one is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 819703@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Tormod Volden <debian.tormod@gmail.com> (supplier of updated xscreensaver package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmaster@ftp-master.debian.org)
> 
> 

Just looked at your fix and find it annoying ...

Please don't ignore jwz's declared intention by just disabling his check.


kind regards,

Harald

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Thu, 21 Apr 2016 14:45:08 GMT) (full text, mbox, link).

Acknowledgement sent to polinacolee@yahoo.co.uk:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Thu, 21 Apr 2016 14:45:08 GMT) (full text, mbox, link).

Message #517 received at 819703@bugs.debian.org (full text, mbox, reply):

i am Polina Cole From UK, i get you through web book i need a good
friendship my email, polinacolee@yahoo.co.uk,

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sat, 23 Apr 2016 02:30:05 GMT) (full text, mbox, link).

Acknowledgement sent to Fred Maranhão <fred.maranhao@gmail.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 23 Apr 2016 02:30:05 GMT) (full text, mbox, link).

Message #522 received at 819703@bugs.debian.org (full text, mbox, reply):

I would like to suggest the change of the annoying message.

alter

"This version of XScreenSaver is very old! Please upgrade!"

to

"This version of XScreenSaver is very old! Please don't send bugreports!"

and I prefer to see this message in debconf, not in every login.

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Tue, 17 May 2016 12:09:04 GMT) (full text, mbox, link).

Acknowledgement sent to duncanvargass@yahoo.com:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 17 May 2016 12:09:04 GMT) (full text, mbox, link).

Message #527 received at 819703@bugs.debian.org (full text, mbox, reply):

i am Duncan Vargas From USA, i get you through web book i need a good
interest my email, duncanvargass@yahoo.com,

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Tue, 24 May 2016 18:48:09 GMT) (full text, mbox, link).

Acknowledgement sent to fdxe004@gmail.com:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 24 May 2016 18:48:09 GMT) (full text, mbox, link).

Message #532 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Kindly View The Attached File

[Delivery.pdf (application/pdf, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Tue, 31 May 2016 11:09:03 GMT) (full text, mbox, link).

Acknowledgement sent to Joost van Baal-Ilić <joostvb@debian.org>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 31 May 2016 11:09:03 GMT) (full text, mbox, link).

Message #537 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Tue, 19 Apr 2016 08:53:06 +0200, Harald Hellmuth wrote:
> Please don't ignore jwz's declared intention by just disabling his check.

Imho, the best way to deal with this is to stop shipping xscreensaver
altogether.

On May 23 2016, jwz wrote in https://www.jwz.org/blog/2016/05/xscreensaver-5-35/ :
> And -- yes -- Dear Debian, please stop shipping xscreensaver

linking to
https://www.jwz.org/blog/2016/04/i-would-like-debian-to-stop-shipping-xscreensaver/
.

He has asked us at least twice.  Time to honor his request, I'd guess.

Bye,

Joost

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Fri, 03 Jun 2016 12:27:04 GMT) (full text, mbox, link).

Acknowledgement sent to rosetherine01@gmail.com:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 03 Jun 2016 12:27:04 GMT) (full text, mbox, link).

Message #542 received at 819703@bugs.debian.org (full text, mbox, reply):

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sun, 10 Jul 2016 23:54:04 GMT) (full text, mbox, link).

Acknowledgement sent to Anders Olausson <Anders.Olausson@malmo.se>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 10 Jul 2016 23:54:04 GMT) (full text, mbox, link).

Message #547 received at 819703@bugs.debian.org (full text, mbox, reply):




________________________________________
Från: Anders Olausson
Skickat: den 11 juli 2016 00:37
Till: Anders Olausson
Ämne: Blessing!‏

I, Liliane Donated 2,000,000 Dollars to you, Contact me on ( lbetten092@outlook.pt ) for more details.

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sat, 30 Jul 2016 18:33:05 GMT) (full text, mbox, link).

Acknowledgement sent to reginafred53@yahoo.com:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 30 Jul 2016 18:33:05 GMT) (full text, mbox, link).

Message #552 received at 819703@bugs.debian.org (full text, mbox, reply):

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Fri, 14 Oct 2016 17:45:03 GMT) (full text, mbox, link).

Acknowledgement sent to "FedEx International Ground" <jeffery.rollins@soposa.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 14 Oct 2016 17:45:03 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sun, 23 Oct 2016 00:48:03 GMT) (full text, mbox, link).

Acknowledgement sent to "FedEx International Next Flight" <lance.helms@elcalendariodelafarmacia.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sun, 23 Oct 2016 00:48:03 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Mon, 24 Oct 2016 06:45:02 GMT) (full text, mbox, link).

Acknowledgement sent to "FedEx 2Day A.M." <cody.peck@msmeconsultant.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Mon, 24 Oct 2016 06:45:02 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Tue, 01 Nov 2016 15:30:06 GMT) (full text, mbox, link).

Acknowledgement sent to "FedEx 2Day" <roberto.mayo@lawnsbybigal.com>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Tue, 01 Nov 2016 15:30:06 GMT) (full text, mbox, link).

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Sat, 12 Nov 2016 05:45:02 GMT) (full text, mbox, link).

Acknowledgement sent to "FedEx International Ground" <brett.vaughan@ztm-arbeitskreis.de>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Sat, 12 Nov 2016 05:45:02 GMT) (full text, mbox, link).

Message #581 received at 819703-done@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Dear Customer,

We can not deliver your parcel arrived at December 14.

Review the document that is attached to this e-mail!

Yours truly,
Warren Nielsen,
Mail Delivery Manager.

[Undelivered-Parcel-ID-000567463.zip (application/zip, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Tormod Volden <debian.tormod@gmail.com>:
Bug#819703; Package xscreensaver. (Fri, 16 Dec 2016 07:36:03 GMT) (full text, mbox, link).

Acknowledgement sent to "ROBAS MORA, MARINA" <marina.robasmora@ceu.es>:
Extra info received and forwarded to list. Copy sent to Tormod Volden <debian.tormod@gmail.com>. (Fri, 16 Dec 2016 07:36:03 GMT) (full text, mbox, link).

Message #586 received at 819703@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

I, Liliane Donated 2,000,000 Dollars to you, Contact me on ( lbetten092@outlook.pt ) for more details.????





================================================??




Este mensaje y sus archivos adjuntos, enviados desde FUNDACIÓN UNIVERSITARIA SAN PABLO-CEU, pueden contener información confidencial y está destinado a ser leído sólo por la persona a la que va dirigido por lo que queda prohibida la difusión, copia o utilización de dicha información por terceros. Si usted lo recibiera por error, por favor, notifíquelo al remitente y destruya el mensaje y cualquier documento adjunto que pudiera contener.

En cumplimiento de la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal, le recordamos que podrá en todo momento ejercitar los derechos de acceso, rectificación, cancelación y oposición sobre sus datos personales que hayan podido ser incorporados en nuestros ficheros a través del envío de un correo electrónico al remitente, especificando en el cuerpo del mensaje la dirección de e-mail sobre la que desea ejercitar su derecho.

Cualquier información, opinión, conclusión, recomendación, etc. contenida en el presente mensaje no relacionada con la actividad de FUNDACIÓN UNIVERSITARIA SAN PABLO-CEU y/o emitida por persona sin capacidad para ello, deberá considerarse como no proporcionada ni aprobada por FUNDACIÓN UNIVERSITARIA SAN PABLO-CEU, que pone los medios a su alcance para garantizar la seguridad y ausencia de errores en la correspondencia electrónica, pero no puede asegurar la inexistencia de virus o la no alteración de los documentos transmitidos electrónicamente, por lo que declina cualquier responsabilidad a este respecto.

This message and its attachments, sent from FUNDACIÓN UNIVERSITARIA SAN PABLO-CEU, may contain confidential information and is intended to be read only by the person to which it is directed. Therefore any disclosure, copying or use by third parties of this information is prohibited. If you receive this in error, please notify the sender and destroy the message and any attachments that it may contain.

In compliance with Law 15/1999, December 13, of Personal Data Protection, we remind you that you may at any time exercise your rights of access, rectification, cancellation and opposition of your personal data that may have been stored in our files by sending an e- mail to the sender, specifying the message body of the e-mail address on which you wish to exercise your right.

Any information, opinion, conclusion, recommendation,... contained in this message and which is unrelated to the business activity of FUNDACIÓN UNIVERSITARIA SAN PABLO-CEU and/or issued by unauthorized personnel, shall be considered unapproved by FUNDACIÓN UNIVERSITARIA SAN PABLO-CEU. FUNDACIÓN UNIVERSITARIA SAN PABLO-CEU implements control measures to ensure, as far as possible, the security and reliability of all its electronic correspondence. However, FUNDACIÓN UNIVERSITARIA SAN PABLO-CEU does not guarantee that emails are virus-free or that documents have not be altered, and does not take responsibility in this respect.

[Message part 2 (text/html, inline)]

Message #589 received at 819703-close@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Dear Customer,



We can not deliver your parcel arrived at December 31.



Review the document that is attached to this e-mail!



Respectfully,

Carlos Mcintosh,

USPS Support Agent.

[Ground-Label-04139869.zip (application/zip, attachment)]

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Sun, 29 Jan 2017 07:24:59 GMT) (full text, mbox, link).

Send a report that this bug log contains spam.

Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sat Jan 6 18:45:49 2018; Machine Name: buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Debian Bug report logs - #819703 xscreensaver: please disable "This version of XScreenSaver is very old! Please upgrade!" message

Debian Bug report logs - #819703
xscreensaver: please disable "This version of XScreenSaver is very old! Please upgrade!" message