Maybe you shouldn't install new software for a bit
1–10 of 497 posts
Re: Maybe you shouldn't install new software for a bit
#2Re: Maybe you shouldn't install new software for a bit
#3Re: Maybe you shouldn't install new software for a bit
#4[flagged]
Re: Maybe you shouldn't install new software for a bit
#5I switched to llama.cpp because of that.
To me it feels more and more that the slopcode world is the opposite philosophy of reproducible builds. It's like the anti methodology of how to work in that regard.
Before, everyone was publishing breaking changes in subminor packages because nobody adhered to any API versioning system standards. Now it's every commit that can break things. That is not an improvement.
Re: Maybe you shouldn't install new software for a bit
#6Re: Maybe you shouldn't install new software for a bit
#7Re: Maybe you shouldn't install new software for a bit
#8It really pisses me off that responsible disclosure timelines are being ignored.
> Because the responsible disclosure schedule and the embargo have been broken, no patch exists for any distribution.
I had to do a double take reading that. It’s written something happened and prevented them from following a schedule but seemingly they chose to release the information. I hope I’m missing something where it was forcibly disclosed elsewhere.
Edit: Moments later I refreshed the homepage and saw the announcement. They do claim to have consulted with maintainers
Re: Maybe you shouldn't install new software for a bit
#9[flagged]
Re: Maybe you shouldn't install new software for a bit
#10It really pisses me off that responsible disclosure timelines are being ignored.
the idea that it exists at all is more or less a gentleman's agreement in the engineering world anyway