I, Liliane Donated 2,000,000 Dollars to you, Contact me on (
lbetten...@outlook.pt ) for more details.
??
Este mensaje y sus archivos adjuntos, enviados desde FUNDACIÓN UNIVERSITARIA
SAN PABLO-CEU, pueden contener información
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 (
lbetten...@outlook.pt ) for more details.
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
i am Duncan Vargas From USA, i get you through web book i need a good
interest my email, duncanvarg...@yahoo.com,
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.
i am Polina Cole From UK, i get you through web book i need a good
friendship my email, polinaco...@yahoo.co.uk,
On Sat, 16 Apr 2016 21:47:59 + Tormod Volden
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
On Wed, Apr 6, 2016 at 1:01 AM, Peter Nowee 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
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
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
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
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
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
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
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
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
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
On Tue, Apr 5, 2016 at 8:31 PM, Tormod Volden
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!
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
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
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
On Tue, 5 Apr 2016 05:16:51 +0200 Peter Nowee 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
>
* 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
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.
>
> 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
As always. Bla bla bla! Don't talk! Fix it in stable or kick it! NOW!
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
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:
On Mon, Apr 04, 2016 at 03:48:44PM +, 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
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
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
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
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
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
On Mon, Apr 4, 2016 at 5:17 PM, Santiago Vila 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
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
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
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
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.
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
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
Hello Santiago,
On Mon, 4 Apr 2016 01:02:01 +0200
Santiago Vila 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
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
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" t
Sorry, the not-so-short patch would be like this.
--- a/driver/demo-Gtk.c
+++ b/driver/demo-Gtk.c
@@ -5292,7 +5292,7 @@ main (int argc, char **argv)
the_network_is_not_the_computer (s);
- if (senescent_p())
+ if (0)
warning_dialog (s->toplevel_widget,
_("Warning:\n\n"
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
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
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
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.
diff -rupN xscreensaver-5.30/driver/demo-Gtk.c xscreensaver-5.30.fixed/driver/demo-Gtk.c
---
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".
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
Hi Yves-Alexis,
On Fri, 01 Apr 2016 21:26:23 +0200 Yves-Alexis Perez 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
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
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".
* 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
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
This warning is offensive, expecially to the new end users, for
professionals that installed them, and Debian community in general.
Please remove.
>> 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
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
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
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"
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
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?
* 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
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
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
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
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
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
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
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
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
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
Please remove XScreenSaver from Debian.
Peter Nowee, please take your sanctimony and go fuck yourself with it.
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
On Fri, Apr 01, 2016 at 11:04:28PM -0400, Holger Levsen wrote:
> On Sat, Apr 02, 2016 at 02:53:30AM +, 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
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 +, 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
Hi,
On Sat, Apr 02, 2016 at 02:53:30AM +, 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.)
--
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,
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
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
[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 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
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 wrote:
> On Fri, 1 Apr 2016 10:10:40 -0700 Jamie Zawinski wrote:
> > For those of you who can't be bothered to read
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.
>
> I stand by my words here: If you are considering removing this warning, then
> I ask that instead, you remove the XScreenSaver
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
> > > (That gives a really bad impression: Jessie is just one year old, we
> > > told the
On ven., 2016-04-01 at 18:54 +0200, Michael Biebl wrote:
> On Fri, 1 Apr 2016 18:11:15 +0200 Samuel Thibault
> 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
> > >
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
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
Description: Digital signature
On Fri, 1 Apr 2016 18:11:15 +0200 Samuel Thibault
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
Hello Samuel,
On Fri, 1 Apr 2016 18:09:53 +0200
Samuel Thibault 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
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,
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
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
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
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
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
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".
Hello, is it joke )?
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
Dear Maintainer,
please update the xscreensaver package in both Jessie and Wheezy.
Thak you,
--
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics
signature.asc
Description: PGP signature
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
1 - 100 of 101 matches
Mail list logo