Live data from Hacker News

“This version of XScreenSaver is very old. Please upgrade”

bugs.debian.org

51–60 of 105 posts

Re: “This version of XScreenSaver is very old. Please upgrade”

#51
post #30
post #23

Frankly, this is a very good example why I inevitably give up on using Debian. It is not the software writers' fault that your distro can't be arsed to keep its package system up-to-date. Even the unstable branch is routinely multiple versions behind on software. The idea of linking end-user software versioning to the operating system version itself was always a dumb idea, but has become even more absurd over time. N…

Maybe distros like Debian are more stability/security oriented than feature oriented. New version of software often contain new features that it may introduce new bugs. Debian guarantees that when you install their distro things are going to work and are kind of secure. The tradeoff of having all the software in the distro being checked by people that have tested and checked that everything works well and smooth it's…

> Maybe distros like Debian are more stability/security oriented than feature oriented. New version of software often contain new features that it may introduce new bugs.

New versions of software also fix old stability and security bugs.

If software became more secure with age, then the older your version of gnome screensaver, the more secure it would be ( https://www.jwz.org/blog/2015/04/i-told-you-so-again/ ).

Re: “This version of XScreenSaver is very old. Please upgrade”

#52
post #34
post #30

Earlier quoted context omitted.

Maybe distros like Debian are more stability/security oriented than feature oriented. New version of software often contain new features that it may introduce new bugs. Debian guarantees that when you install their distro things are going to work and are kind of secure. The tradeoff of having all the software in the distro being checked by people that have tested and checked that everything works well and smooth it's…

Spot on. I was always puzzled why some software just can't come statically compiled. I suppose not all apps can be distributed like that, but most of them can. I can't even remember how many hours I wasted on trying to compile a new version of some program, just to learn the infinite tree of dependencies, newer versions of existing libraries required, build prefixes tweaking etc... Most of that time could have been s…

Because statically linking everything has several negative consequences:

  * increased storage space
  * increased memory usage
  * increased downtime for updates (since more files have
    to be updated)
  * increased bandwidth usage (total size of download
    for update)
  * potentially increased security risks
In short, trading off all of the above to simply avoid proper release engineering and simplified dependency management is the wrong answer.

Our systems need less downtime and better security; not the opposite, which is what static linking brings.

That's why Solaris, as an example, does not provide static archives for almost any of the components that are provided, especially libc.

Re: “This version of XScreenSaver is very old. Please upgrade”

#53
post #29

Man, it's really weird to see this after just installing Debian after using arch for about a year. And sure enough, that message popped up, I tried to update it and the repos were outdated. Brother.. My worst experience with their repos was with logstash having a bug where it would annoyingly install logstash-web with an auto-start. But..... the package had a typo in its startup script and caused the JVM to restart o…

Debian does not have a logstash or logstash-web package. When complaining about "their repos" did you mean elastic.co's repos?

Re: “This version of XScreenSaver is very old. Please upgrade”

#54

I'm more on the BSD-side, so can someone give an explanation on why bug fixes are not being back ported? I understand long term stable, but I thought that was more an API thing.

There's no policy against backporting bugfixes, it just doesn't always happen due to lack of developers. If upstream doesn't provide backported bugfixes, it requires someone else to volunteer the time/resources to do it. For some packages, companies sponsor long-term maintenance branches, or particularly interested volunteers take it upon themselves to do it. For other packages, nobody steps up to do the work, so it…

Oh yeah, depending on which one, its a bit slow on the BSD side also. I was just looking at why you wouldn't back port bug fixes as a matter of policy, but I'll take your comment as truth although it seems the conversation in the thread is a bit odd on that point. Thanks.

Re: “This version of XScreenSaver is very old. Please upgrade”

#56
post #23

Frankly, this is a very good example why I inevitably give up on using Debian. It is not the software writers' fault that your distro can't be arsed to keep its package system up-to-date. Even the unstable branch is routinely multiple versions behind on software. The idea of linking end-user software versioning to the operating system version itself was always a dumb idea, but has become even more absurd over time. N…

  > No other operating system but Linux (and possibly some 
  > BSDs) does this to the extent that the distro model does.
I am not sure this is the case. What other operating systems except Linux and the BSDs offer users a choice for which XYZ should be used? Is the window manager functionality in Windows Vista not provided by a specific version of that software component? I think the version of OpenSSH in OSX is tied to the version of OSX? You don't recognize this in non-Linux+BSDs because you don't have a choice, you use whatever version of XYZ comes with your OS.

  > Even the unstable branch is routinely multiple versions 
  > behind on software.
Respectfully, I think this is a bit of an exaggeration. Maybe this is true for esoteric packages but I am curious to hear why you think this. Unstable has the latest Xscreensaver at the moment. There was a one day lag between the release of 5.34 and a packaged version for unstable.

Re: “This version of XScreenSaver is very old. Please upgrade”

#57

Earlier quoted context omitted.

I think that's basically how all the X11 screenlockers work, sadly.

Yes. But xscreensaver only use straight xlib to paint any UI elements. JWZ's argument is that this reduce the chance of bugs vs using the likes of GTK or Qt to draw password prompts etc.

I don't think he meant to say it was flawless, but I'm sure you agree it reduces the attack surface by a great deal.

Re: “This version of XScreenSaver is very old. Please upgrade”

#58

Earlier quoted context omitted.

I think that's basically how all the X11 screenlockers work, sadly.

Yes. But xscreensaver only use straight xlib to paint any UI elements. JWZ's argument is that this reduce the chance of bugs vs using the likes of GTK or Qt to draw password prompts etc.

Looking at bug tracker activity so far would suggest that it does, but of course, the stats might be skewed by far more people using a Gnome/Unity/Cinnamon/whatever-ified version of xscreensaver than the vanilla one.

I read about that bug a while ago. It was due to mishandling a strange X11-specific cornercase; to be fair, that's the kind of stuff that is certainly more aptly handled (in the X11 world) in a toolkit (X11-specific cornercases are like 30% of the reason why, as soon as alternatives to Xlib were available, everyone embraced them and cried tears of joy), which would suggest that not relying on toolkits opens xscreensaver's locker to other issues that are more aptly handled in a toolkit.

However, if you look over the bugs that Gnome, Cinnamon or Unity's wrappers had... I'm inclined to think that there are a lot more trivial problems (like the one I linked in my other comment, here : https://news.ycombinator.com/item?id=11412688 ) in Gnome's a thousand and one libraries than there are cornercases in X11.

Re: “This version of XScreenSaver is very old. Please upgrade”

#59
post #51
post #30

Earlier quoted context omitted.

Maybe distros like Debian are more stability/security oriented than feature oriented. New version of software often contain new features that it may introduce new bugs. Debian guarantees that when you install their distro things are going to work and are kind of secure. The tradeoff of having all the software in the distro being checked by people that have tested and checked that everything works well and smooth it's…

> Maybe distros like Debian are more stability/security oriented than feature oriented. New version of software often contain new features that it may introduce new bugs. New versions of software also fix old stability and security bugs. If software became more secure with age, then the older your version of gnome screensaver, the more secure it would be ( https://www.jwz.org/blog/2015/04/i-told-you-so-again/ ).

> New versions of software also fix old stability and security bugs.

Sometimes new versions of software fix bugs, sometimes they improve stability, sometimes they introduce new bugs, sometimes they decrease the performance, sometimes they become bloatware, sometimes several of this things happen in any combination.

Re: “This version of XScreenSaver is very old. Please upgrade”

#60
post #34

Earlier quoted context omitted.

Spot on. I was always puzzled why some software just can't come statically compiled. I suppose not all apps can be distributed like that, but most of them can. I can't even remember how many hours I wasted on trying to compile a new version of some program, just to learn the infinite tree of dependencies, newer versions of existing libraries required, build prefixes tweaking etc... Most of that time could have been s…

Because statically linking everything has several negative consequences: * increased storage space * increased memory usage * increased downtime for updates (since more files have to be updated) * increased bandwidth usage (total size of download for update) * potentially increased security risks In short, trading off all of the above to simply avoid proper release engineering and simplified dependency management is…

Thank you for enumerating those downsides. Clearly I'd avoid statically linked software if I would have the option to use `apt-get install` to get that software.

But in the situation that a new version of the software is released, and I think it would benefit me right now, I'd trade all those downsides for being able to use that software right now than waiting to be included in my distro (like it happened to me with Gimp some years ago).

I'm plenty of memory, storage and bandwidth but not so much of time to compile it by hand.

I have to admit that this is just a workaround while we find a better software release and dependency management system.

Post reply on HN