https://socially.drinkingatmy.computer/objects/4df5b6b4-102f-4854-8721-480d56380e0c
I use debian btw 🙈
I like debians dad bud 😻
Awww, mocking my favourite distro. Tried so many. Not a fan of persistent tinkering. I use Debian because it’s awesome for me and my family to use as daily driver.
I use Aaaaaarrrrrchhhh.
Debían DILFs interact
Checks out.
I am a dad who makes that sound and also use debian.
😭😭😭 debian is a treasure and we will all be worse off if you succeed in bullying it
But I want my computer for dicking around in the garage, mowing the lawn. and getting a fresh beer. Involuntary dad noises are the prelude for all that. This is the best ad copy for a distro I’ve ever heard. Next you’re gonna tell me it’s predictable and stable and stoically gets things done.
I use fedora as a daily driver and debian for everything that just needs to do one thing for possibly decades to come with as little maintenance as possible.
I would use Debian more if I didn’t have to remember whether to use
aptoryumevery time I ssh’d into a random server on my network.Fedora KDE for my personal machines, Debian for my servers
Hello fellow KDE enjoyer.
get this, what if your daily driver needed as little maintenance as possible?
Sometimes, you do need some newer packages (e.g. for gaming), and Debian is … not very good at facilitating that, even if it’s usually possible, in theory, to install newer packages from Sid. Flatpaks or manually installing stuff through git etc. help, but that doesn’t work well for stuff like GPU drivers.
My set of requirements for a daily driver is very different. From experience, I’ll end up with a frankendebian that requires much more manual intervention and has a high risk of breaking during updates.
fair point. I fucked my install trying to make my overheating issues go away, but after going onto nobara, pika os I think the issues are here to stay. I’m going to try to stop overtinkering to stop getting frankendebian
i still don’t know what to do with my frankendevuan 😭
As a dad who makes said noises, and a linux devotee, I approve.
Fellow dad who makes said noises here. Debian is my primary OS, and it’s just the way I like it.
I’ve been using Debian for so many years (damn, I feel so old).
Since 2002 here. Now get off my lawn.
I switched to Debian when version 1.1 was released in 1996 and it’s been Debian since then for me, but you youngsters may stay on my lawn as long as you just don’t litter.
i heard about debian in 02! but i was a sophmore more worried about zsnes on windows ME and trying to grow a mustache.
i rent a lawn
Debian is so boring (I love it from the bottom of my hearth and use it in all my servers and personal laptop)
For me debian sounds more like a steam roller. It just works. I installed debian on my first laptop 20 years ago and I know that if I just kept dist-upgrading it every day it would still be running today.
As a dad who mostly runs Debian… Yeah I can’t deny it.
Still my top preferred for stability though!
i use a fedora, like a peep not just getting off the couch - but goin out and doin stuff-
Same. I used to like the thrill of shit breaking at the drop of a fart, but now I just want something that runs a good markdown compatible writing software.
I lost a lot of respect for Debian due to the way they handled the whole issue with xscreensaver.
That’s a super long thread, is there a good summary somewhere for those of us who suffer from “bookmark this for later and then never revisit it” flavors of neurodivergence?
The gist of it is jwz, the maintainer of xscreensaver, received a ton of bug reports for bugs he fixed ages ago because Debian refused to update to a newer version citing “stability” as a reason. He added a warning dialog to his software to warn users that they are running an outdated version and to not report bugs to him. Debian maintainers patched it out because they are legally allowed to do so according to the license. I consider this is GNOME level of assholery. They decided on a shitty policy and then made it someone else’s problem.
Having just read the whole thread;
xscreensaver developer jwz added an allcaps/all bold notification to xscreensaver that says that the current xscreensaver version is really old. This notification could not be user canceled / okayed through. The author did this because he apparently received several emails about xscreensaver versions that were years out of date.
Debian stable’s policy is to make no updates unless they are security or bug related. This directly conflicted with jwz’s policy of only supporting the latest version of xscreensaver.
The Debian maintainers chose to remove the unskippable warning as the other options were harder to maintain / worse to use. This was specifically permissable in the xscreensaver license, but against the authors stated wishes to have xscreensaver removed entire if the warning could not be kept or the software could not be updated.
Of note, jwz escalated to yelling at the first reporter about this in his first email and swearing at another reporter in his second. The Debian stable team offered suggestions which would direct Debian users to the Debian development team for bug reports about the old versions of xscreensaver, but jwz’s hostile approach made that not happen at all.
If I install debian stable it’s because I want it to work, and to not be bothered about anything that doesn’t need to happen. That’s whole point of having Debian stable around. One of the points made in the discussion, which I strongly agree with, is that Linux software is managed in a repository, not individually. A windows program telling me out of date is obnoxious, but expected. A Linux program telling me it is out of date is a obnoxious and unexpected. (Fucking discord…)
The xscreensaver author shot himself in the foot with this one; presumably he wanted to avoid being harrassed over old versions of xscreensaver. What he ended up doing was telling everyone with an old version of xscreensaver that they need to update and then guaranteed they would harass thim about it by not giving the users an option to ignore and walk away from the message.
I consider jwz response entirely reasonable. The initial message immediately suggests going against his wishes and the rest of the thread is about whats good for Debian which is a project that jwz never wanted to be involved in but suddenly its his problem. If I where in his situation I would tell them to go fuck themselves as well. Its just incredibly disrespectful to the person who did the actual work.
The initial message immediately suggests going against his wishes and the rest of the thread is about whats good for Debian
Well yeah. This whole thread was started in the Debian bug tracker. Of course the focus is going to be on what’s good for Debian. The fact that jwz showed up immediately means they followed the Debian bug tracker, which begs the question, why would jwz subscribe to that if they didn’t want to be there? It also sets the tone for the whole discussion. Original reporter was whiny, but, like, it was directed at the Debian team, not jwz. jwz chose to insert themselves into the Debian bug tracker discussion, and also chose to be aggressive about it.
If I where in his situation I would tell them to go fuck themselves as well. Its just incredibly disrespectful to the person who did the actual work.
That’s fair, honestly. jwz owes the Debian team fuck all. But the other half of that is that the Debian team tried to work out a middle of the road solution and were met with immediate hostility.
You can’t work with someone who doesn’t want to work with you, so you do what’s best for your project and just move on.
Doesn’t seem like there where any great replacements for XFCE’s screensaver without potentially breaking things.
Debian isn’t the only stable distro, it and distros like it fill an inarguably societally important role at this point. Its reasonable to not push patches unrelated to bigfixes and security to a stable distro.
Its also reasonable to expect a developer to figure out a way to send canned responses to bug reports, and also require a version number with bug reports, throwing out any with missing or outdated versions. You know, because there are going to be people with outdated computers no matter what their distro does. Who knows, maybe I’m crazy.
[…] Debian maintainer had inadvertently reduced the number of possible keys that could be generated by a given user from “bazillions” to a little over 32,000.
That’s really bad. It also seems like they patched OpenSSL without ever intending to upstream the changes.
The openssl change was communicated with upstream at the time, but no one from upstream pointed out the issue (not surprisingly, because the change seemed like an innocuous fix to an unassigned variable.)
We (Debian) fix bugs and send upstream the changes all the time, so this kind of thing happens. (Upstreams introduce these kind of bugs too; it’s the nature of software development.)
Given the number of times I’ve had to triage issues caused by mispackaged Debian builds, I’m baffled that Debian maintainers are under the impression that their users generally know they’re supposed to report problems to the package maintainers rather than upstream. Maybe people who’ve been using Debian since the naughties do, but for the average user, Debian seems to be crafted specifically to generate duplicate upstream issue reports.
This is a challenge all distributions have which want to keep stability, which means shipping older versions (ideally with long term support) with only security updates for the lifetime of the distribution. It’s totally ok for upstream developers to not support any of those old versions too; they’re not being paid either.
It hasn’t committed suicide in me yet.
Software app just pinwheels though, but apt works.
This is the first thing I have actually learned about Debian lmao I already respect it
