When I said "article," I guess I meant that I don't want to watch a youtube video detailing the drama or whatever, I was hoping to just read about it. Either way, thanks for the link and the explanation further down the thread.
Considering that I've spent many a night at Bootie SF (back when it was at DNA Lounge) on too many drugs or alcohol to respond to on-call issues, it's entirely possible that he had more power over tech than it had over his life.
Like many people in San Francisco, he is an intelligent guy with great will to power and eccentric views.
It's an eggcup.
Breathe.
Many of whom share his same opinion on VCs and late stage capitalism.
wait, this would be a bad thing?
I don't hate him and didn't write anything of the sort. I've never met him. He might as well be the tooth fairy or the Easter bunny as fas as I'm concerned.
> the fact remains that probably 95% of ycombinator funded startups couldn't exist without making extensive use of the gpl, bsd, Apache and similar licensed software produced by a lot of open source curmudgeons and greybeards. Many of whom share his same opinion on VCs and late stage capitalism.
I've been using FOSS for personal use since I was a child. I'm a literal card-carrying supporter of the FSF. I'm more passionate about it than I am shitting on random people on the internet. If he has a problem with VCs then he can spam them with pictures of genitalia and ad-hominem attacks, not me, who's just some random dude who _isn't_ worth millions of dollars from a software business exit (along with thousands of others on this site).
Not that I would seek to deny your valid annoyance and offense. It's a non-consensual scrotum in a teacup. I personally would have gone a different direction, I get why that would raise someone's hackles.
Highly recommend installing https://addons.mozilla.org/en-US/firefox/addon/smart-referer
<https://jwz.org/blog/2016/04/i-would-like-debian-to-stop-shi...>
- https://bugs.gentoo.org/101619
- https://bugs.gentoo.org/124595
And Quod Libet vs. Debian (2007):
https://web.archive.org/web/20070307113840/http://modeemi.fi...
There's plenty of other examples, of course - one that springs to mind was when Ubuntu shipped a patch of their own design in OpenZFS that caused data loss, and it got reported to upstream.
And credit to Fedora, it looks like they're working quickly to fix the problem now. It's pretty obvious it wasn't malice that led them to not respond quickly.
So stupidity then.
Seems legit.
I’m a Fedora packager (not for this package). Like many others I have an unrelated day job.
If there’s an upstream complaint I might get to it this weekend, maybe next. If I’m busy for a few weeks that doesn’t make me stupid.
Have had my share of “discussions” with upstream who want the latest version packaged when this might not be completely in line with our guidelines. Not an uncommon issue.
But equally, I don’t think it’s fair that packagers want to have it both ways. Packagers want to make subtle, possibly breaking changes to software they didn’t author. The end users feel the pain and complain to the author. The author has no control over the situation, and they’re feeling the pain during the working week.
So the packager has been instrumental in creating the problem with the patch, and when requested to do something about it, turns around and says “buddy I do this for free, I’ll get to it over the weekend, maybe.” Sure, but the author is feeling the pain right now.
Again, it’s nice that you’re volunteering your time for others. But it would be good if you acknowledged that the costs of packaging aren’t borne entirely by packagers. Authors bear part of the cost when they get blamed for broken software.
I suppose my advice to upstream would be to direct the end user to the Fedora bug tracker, where the bug can land in my queue. Or advise the user to install from a different source.
The upstream that I’ve dealt with have been kind enough to lodge a bug themselves on the package I look after, which is also an option, and much appreciated.
How is upstream supposed to make this happen when distro maintainers not only don't mark the package as modified by them, but also silently change the flatpak configuration so that installing packages from flatpak in the way that would normally install a clean upstream build doesn't do so?
Less of a poor faith comment, more like a badly landed gag. In my head, everybody would have known I was riffing off:
"Never attribute to malice that which is adequately explained by stupidity." -- https://en.wikipedia.org/wiki/Hanlon%27s_razor
I vaguely remember this happening but I’d need to check.
This grossly understates the problem.
The debian xscreensaver package was years old, and contained bugs related to screen locking which were an actual security issue.
Your comment is in very poor taste.
In contrast, Red Hat Enterprise Linux, a distro funded by IBM and countless faceless backers, has recently stopped patching many vulnerabilities, recommending to their users to rely on mitigations instead, despite the availability of upstream patches.
Furthermore, the recent vulnerability threatscape is inundated with CVE hunters who are desperate to call the most minor degradation of service a vulnerability. For a community project (and apparently an enterprise-serving megacorporation), this causes patching fatigue.
I'm not really sure why everyone is focusing on that phrase, though. I think it's pretty clear if you read any of the source material, as said, that that is not an accurate representation of what was going on, and I would have also expected "every 30 minutes" to be a pretty clearly hyperbolic expectation for anyone to process updates after.
Is everyone focusing on the phrase? I thought I asked about it, and that's all that's happened.
> I would have also expected "every 30 minutes" to be a pretty clearly hyperbolic expectation for anyone to process updates after
I couldn't imagine a benign use of hyperbole in timeliness when some expectations of timeliness are silly, and some are sensible. I thought I'd ask, in case there was a good faith reason for it, rather than just assume you're trying to use insinuation to change people's minds.
So they grossly understate the problem, make it seem like it’s the person authoring the software at fault or the one who’s being unreasonable.
They’re quick to tell you how great the maintainers are, how much effort they put in for free but they don’t share that same love for the author of the package. You know, the person who actually wrote the software. They don’t acknowledge that without the author they’d have no software to begin with, and that providing support to older versions of software is a cost to the author. Not just older, but possibly broken in subtle ways because of the patches applied on top. The author still gets all the blame and all the support requests for changes they didn’t make.
To be clear, there’s nothing wrong with wanting to run old, stable software. No one questions that their distro is “the most stable”. That they cannot or will not see the costs of doing so on the author is a shortcoming, but there’s no solving that.
> To be clear, there’s nothing wrong with wanting to run old, stable software.
I personally run on latest, apply all updates zealously within a week or two.
They have different goals/purposes, often, and they frequently don't line up with my own.
Maintainers are exhausting in their own right, they do a ton of work and so they think their decisions are more important because of the work they do, user be damned...
Authors usually only care about their version of the software.
I think, a better medium, would be if a third party is packaging an application, perhaps they should always explicitly state they are the ones packaging it. Then there is less confusion.
Or, you know, let the author keep control of that...
That's rich, coming from a project very closely tied to Gtk, which has a history of massive breaking changes, and outright removing functionality, leading to many projects continuing to use older versions of gtk for a very long time.
I believe they mainly remove functionality between major releases of GTK, not within a release. Can you cite an example where they have done this between gtk minor releases ? Aka gtk 3.1 -> 3.2 ?
Fedora KDE is literally release blocking and has been approved for promotion to be on the same level as Fedora Workstation.
Red Hat isn't as involved with Qt, which is mainly maintained by yhe Qt group company.
RedHat employees make the majority of commits to Gtk and I think are some of the maintainers/managers?
Why do they still mingle with sw distributions? Wasn't the sandboxed blob trend born also to try blackbox strategies and have parallel versions without dealing with too much hell? Was that laziness/economical advantage (EOL'd library, no business in porting fixes, upgrade to the latest and greatest) or something else?
For this reason I don't understand why did they changed the library in there (that build of OBS wasn't broken because of system-wide libs, it was because allegedly they changed the lib in the flatpak), whatever the security hole couldn't they block it "from the outside"?
For those who don't have that in their context - jwz got very upset at people reporting bugs against xscreensaver that had been fixed for a long time in upstream but e.g. Debian doesn't just ship upstream updates every 30 minutes. He requested Debian stop shipping it (or update it? I didn't go reread the entire chain before replying), Debian declined.
He then put in a piece of code that popped up a notification if the system time was sufficiently far past the hardcoded value, informing people they should upgrade, and Debian debated patching his message out.
[1] - jwz dot org/blog/2016/04/i-would-like-debian-to-stop-shipping-xscreensaver/
(Link turned into not a link because I had forgotten how jwz feels about HN referrers.)